ENR 1.6 ATS SURVEILLANCE SERVICES AND PROCEDURES

1  Primary Radar
1.1  General
1.1.1 Generally, the UK subscribes to the procedures for the use of ATS surveillance systems in the provision of ATS which are detailed within PANS-ATM (Doc 4444). Exceptions are the ATS surveillance service provided to VFR flights in class E airspace, and to all flights in class G airspace. These arrangements are described in ENR 1.1 paragraph 2 and summarised in ENR 1.6 paragraph 1.2.
1.2  Types of ATS Surveillance Service
1.2.1  ICAO References

Doc 4444, paragraph 8.

1.2.2 The provision of an Air Traffic Service is dependent upon specific types of airspace. Details of the services provided are stated in the table below.

Table (see also maps at ENR 6-9, ENR 6-10, ENR 6-70 and ENR 6-71).

Type of Airspace

Type of Service

ATC action with regard to Unknown Aircraft that may be in Unsafe Proximity to the Aircraft in Receipt of an Air Traffic Service

Class A, C and D Airspace.

Radar Control Service

If ATS surveillance system derived, or other information, indicates that the unknown aircraft is lost, has experienced radio failure or is making an unauthorised penetration of the airspace - avoiding action shall be given and traffic information shall be passed.

Class E Airspace, Controlled Airspace in which VFR flight without ATC clearance is permitted.

Pass traffic information unless the controller's primary function of sequencing and separating IFR flights is likely to be compromised.

Avoiding action will be given at the request of pilots but to limits decided by the controller or if information has been received which indicates that a position indication/symbol may be a particular aircraft that is lost or experiencing radio failure.

Class G Airspace
and
Temporary Reserved Areas and all other airspace.

Deconfliction Service
or
Traffic Service

Traffic information will be passed followed by advice on avoiding action.
or
Traffic information will be passed but no avoiding action is to be given. The pilot is responsible for his own separation.

1.3  ATS Surveillance Service Outside Controlled Airspace
1.3.1  London Control - Requests for Deconfliction Service or Traffic Service
1.3.1.1 In order to avoid excessive RTF conversations on the frequencies used by 'London Control', pilots who intend to request such a service from 'London Control' are to make their initial request on the London Information frequency appropriate to their geographical position. The FISO will co-ordinate with the appropriate Radar Sector and subsequently inform the pilot whether or not a Deconfliction Service or Traffic Service can be provided and, if so, on what frequency.
1.3.1.2 Pilots should note that no Deconfliction Service or Traffic Service will be available on any London Control Frequency below FL 70. In any case a serviceable transponder will be a pre-requisite for either service.
1.4  Radar Vectoring — Controlled Airspace
1.4.1 At certain aerodromes where the associated Controlled Airspace does not encompass the Surveillance Minimum Altitude Area (SMAA), aircraft may be vectored outside the notified airspace for approaches to certain runways. The aerodromes and runways to which this procedure may apply are listed below:

Aerodromes

Runways

Aerodromes

Runways

Bournemouth

08

Prestwick

20

Leeds Bradford

14Southend05/23
London/City27Teesside International 05
1.5  Radar Vectoring for ILS Approach
1.5.1  ICAO Reference

Doc 4444, Chapter 8, paragraph 8.9.4.

1.5.2 Aircraft being positioned for final approach will be given a heading to close with the localizer at a range of at least 5 NM from the runway threshold and at a level below the glide path. The pilot will be told to complete the turn on and to report established on ILS, but at this point if he requests it, ATC will give another vector to bring the aircraft on to the localizer. If the pilot wishes to lock himself on to the localizer, he must ask permission from ATC when there is still time for the action to take place without crossing the localizer.
1.5.3 On occasions in order to maintain the correct spacing between aircraft, ATC will deliberately vector the aircraft through the localizer for approach from the other side. Pilots will be warned when this manoeuvre is being given.
1.6  Terrain Clearance
1.6.1  ICAO Reference

Doc 4444, Chapter 8, paragraphs 8.6.5.2 and 8.6.5.3.

1.6.2 Controllers will ensure that levels assigned to IFR flights when in receipt of a Radar Control Service will provide at least the minimum terrain clearances given below:
1.6.2.1 Within 30 NM of the radar antenna but excluding the Final and Intermediate Approach Area: 300 M above any fixed obstacle which is closer than 5 NM to the aircraft or which is situated within the area 15 NM ahead of and 20 degrees either side of the aircraft's track. These distances may be reduced to 3 NM and 10 NM respectively where official CAA approval has been promulgated. Levels assigned to aircraft during initial approach will also provide this terrain clearance.
1.6.2.2 Outside 30 NM from the Radar Antenna, for flights on Airways, 300 M above any fixed obstacle within 15 NM of the centre-line; otherwise 300 M above any fixed obstacle within 30 NM of the aircraft.
1.6.2.3 Radar Controllers have no responsibility for the terrain clearance of, and will not assign levels to, aircraft operating Special VFR or VFR within controlled airspace which accept radar vectors.

Note: In sections of ATS Routes where the base is defined as a Flight Level, the lowest usable level normally provides not less than 1500 FT Terrain Clearance.

1.6.3 Within Class G Airspace, regardless of the service being provided, pilots are ultimately responsible for terrain clearance.
1.6.3.1 A Deconfliction Service shall only be provided to aircraft operating at or above the ATC unit's terrain safe level, unless on departure from an aerodrome when climbing to the ATC unit's terrain safe level, or when following notified instrument approach procedures.
1.6.3.2 Subject to ATS surveillance system coverage, a Traffic Service may be provided below ATC unit terrain safe levels. However, levels allocated by controllers shall be terrain safe unless an agreement is reached with the pilot, or such levels form part of VFR clearances for aerodrome arrival or to enter controlled airspace that by necessity require flight below the unit terrain safe levels. Controllers shall only instigate heading allocations when the aircraft is at or above an ATC unit's terrain safe level. However, if pilots request a heading from the controller whilst operating below the ATC unit terrain safe level, this may be provided as long as the controller reminds the pilot that he remains responsible for terrain clearance.
1.6.4  ATC Surveillance Minimum Altitude Charts
1.6.4.1 In November 2007, ICAO introduced new charting requirements for the depiction of minimum altitudes issued by a controller providing an ATC Surveillance service under the title ATC Surveillance Minimum Altitude Chart (ATCSMAC). The purpose of the ATCSMAC is to provide information that will enable flight crews to monitor and cross check altitudes assigned whilst receiving vectoring instructions from air traffic controllers.
1.6.4.2 In the UK, the ATCSMAC depicts the Surveillance Minimum Altitude Area(s) in the vicinity of a designated aerodrome. For the purposes of the UK application of ATCSMACs, the following definition of a Surveillance Minimum Altitude Area (SMAA) will apply:

‘A Surveillance Minimum Altitude Area is a defined area in the vicinity of an aerodrome, in which the minimum safe levels allocated by a controller vectoring IFR flights with Primary and/or Secondary Radar equipment have been predetermined.’

1.6.4.3 Charts for individual aerodromes appear in the AIP Aerodrome Section (AD 2-EGXX-5-1). Each chart includes the following:
  1. Outline of the Surveillance Minimum Altitude Area(s);

  2. significant obstructions and spot heights;

  3. minimum initial altitudes within the Surveillance Minimum Altitude Area(s) and detailed geographic delineation;

  4. Final Approach Tracks;

  5. Intermediate Approach Areas (where appropriate);

  6. aerodrome elevation;

  7. Transition Altitude;

  8. Missed Approach instructions;

  9. loss of communication procedures.

1.6.4.4 Further information about the criteria used in the design of ATCSMACs will be included in CAP 777 - ATC Surveillance Minimum Altitude Charts in UK Airspace, Policy and Design Criteria.

CAP 777 is available at: www.caa.co.uk (Publications).

1.7  Navigational Assistance
1.7.1  ICAO Reference

Doc 4444, Chapter 8, paragraph 8.6.6.

1.7.2 In order that a controller may provide the most appropriate advice/instructions, the pilot of an aircraft requesting navigational assistance when in receipt of an ATS surveillance service shall state the reason (eg to avoid areas of adverse weather or unreliable navigational instruments) and giving as much information as possible in the circumstances.
1.7.3 Identified aircraft operating within controlled airspace are deemed to be separated from unknown aircraft flying in adjoining uncontrolled airspace. However, whenever practicable the controller will aim to keep aircraft under his control at least 2 NM within the boundary of controlled airspace.
1.8  Weather Avoidance
1.8.1  ICAO Reference

Doc 4444, Chapter 8, paragraph 8.6.9.

1.8.2 In order to avoid weather, if a controller considers it expedient for the aircraft to leave controlled airspace, the pilot will be advised and will be responsible for accepting the detour into uncontrolled airspace.
1.8.3 In controlled airspace, a pilot using an aircraft radar and intending to detour around observed weather, must obtain a clearance from the controller before doing so. Under these circumstances, if it is necessary to leave controlled airspace the pilot must request permission to re-join.
2  Secondary Surveillance Radar (SSR)
2.1  General
2.1.1 In accordance with the Air Navigation Order, a SSR Mode S transponder shall be operated within the airspace notified at GEN 1.5, paragraph 5.3.1. In all other airspace, when a serviceable SSR transponder is carried, a pilot shall operate the transponder at all times during flight, regardless of whether the aircraft is within or outside airspace where SSR is used for ATS purposes in accordance with SERA.13001(a) and should enable pressure-altitude reporting if available, in order to facilitate detection of their aircraft by collision avoidance systems and ATS surveillance equipment.
2.1.2 Except for flight in airspace designated by the CAA for mandatory operation of transponder, aircraft without sufficient electrical power supply are exempted from the requirement to operate the transponder at all times.
2.1.3 In airspace where the operation of transponders is not mandatory, pilots of suitably equipped aircraft shall comply with paragraph 2.2.2.1.2.
2.1.4 With the exceptions detailed in paragraph 2 pilots shall:
  1. If proceeding from an area where a specific Mode A code has been assigned to the aircraft by an ATS Unit, maintain that code setting unless otherwise instructed;

  2. select or reselect Mode A codes, or switch off the equipment when airborne only when instructed by an ATS Unit;

  3. acknowledge Mode A code setting instructions by reading back the code to be set;

  4. select Mode C pressure-altitude reporting mode of the transponder simultaneously with Mode A unless otherwise instructed by an ATS Unit;

    Note: Where the term Mode C pressure-altitude reporting is used, the information and requirements also apply to pressure-altitude reporting employed by Mode S transponders in response to interrogations from Mode S radars.

  5. when reporting levels under routine procedures or when requested by ATC, state the current altimeter reading to the nearest 100 FT. This is to assist in the verification of Mode C pressure-altitude reporting data transmitted by the aircraft.

    Note: If, on verification there is a difference of more than 200 FT between the level readout and the reported level, the pilot will normally be instructed to switch off the Mode C pressure-altitude reporting mode of the transponder. If independent switching of Mode C pressure-altitude reporting is not possible, the pilot will be instructed to select Mode A code 0000 to indicate a transponder malfunction.

2.2  Special Purpose Mode A Codes
2.2.1 Some Mode A codes are reserved internationally for special purposes and should be selected as follows:
  1. Code 7700. To indicate an emergency condition, this code should be selected as soon as is practicable after declaring an emergency situation, and having due regard for the over-riding importance of controlling aircraft and containing the emergency. However, if the aircraft is already transmitting a discrete code and receiving an air traffic service, that code may be retained at the discretion of either the pilot or the controller;

  2. Code 7600. To indicate a radio failure;

  3. Code 7500. To indicate unlawful interference with the planned operation of a flight, unless circumstances warrant the use of Code 7700;

  4. Code 1000. To indicate an aircraft conducting IFR flight as GAT, where the downlinked aircraft identification is validated as matching the aircraft identification entered in the flight plan;

  5. Code 2000. When:

    1. entering United Kingdom airspace from an adjacent region where the operation of transponders has not been required; or

    2. when operating within United Kingdom airspace in accordance with IFR and is either not receiving an ATS or has not received a specific instruction from ATS concerning the setting of the transponder; or

    3. unless instructed otherwise by ATS, Mode S transponder equipped aircraft on the aerodrome surface when under tow, or parked and prior to selecting Off or STBDY.

  6. Code 7007. This code is allocated to aircraft engaged on airborne observation flights under the terms of the Treaty on Open Skies. Flight Priority Category B status has been granted for such flights and details will be published by NOTAM.

    Note: The Mode C pressure-altitude reporting mode of the transponder should be selected with all of the above Mode A codes.

2.2.2  Mode A Conspicuity Codes
2.2.2.1  General Conspicuity Codes
2.2.2.1.1 When operating at and above FL 100 pilots of aircraft shall select the relevant Mode A conspicuity code (see paragraph 2.2.2.1.3) and the Mode C pressure-altitude reporting mode of the transponder except:
  1. When receiving a service from an ATS Unit or Air Surveillance and Control System Unit which requires a different setting;

  2. When circumstances require the use of one of the Special Purpose Mode A codes or one of the other specific Mode A conspicuity codes assigned in accordance with the UK SSR Code Allocation Plan as detailed in the table at paragraph 2.6 of ENR 1.6.

2.2.2.1.2 When operating a SSR equipped aircraft below FL 100 in circumstances where the operation of SSR transponders is not mandatory, pilots shall select the relevant Mode A conspicuity code (see paragraph 2.2.2.1.3) with Mode C pressure-altitude reporting if available, except:
  1. As in sub-paragraphs 2.2.2.1.1 (a) and 2.2.2.1.1 (b); or

  2. When selecting a Monitoring Code (see paragraph 2.2.5).

2.2.2.1.3 Types:

*7000 – VFR conspicuity code: when operating within United Kingdom airspace in accordance with VFR and have not received a specific instruction from ATS concerning the setting of the transponder.

*2000 – IFR conspicuity code: when operating within United Kingdom airspace in accordance with IFR and have not received a specific instruction from ATS concerning the setting of the transponder.

2.2.2.2  Other Conspicuity Codes
2.2.2.2.1 In addition to Special Purpose Codes and the General Conspicuity Codes detailed above, there are a number of other conspicuity codes in the UK SSR Code Allocation Plan, as detailed in the table at paragraph 2.6 of ENR 1.6. For ease of reference, those not specific to particular locations or ATS Units are listed in the table below:

Code

Use

Conditions/Remarks

*0024

Radar Flight Evaluation/Calibration

Aircraft conducting radar evaluation/calibration flights shall only squawk 0024 for the duration of the trial. The code shall not be used whilst transiting to/from the trial; in such circumstances the appropriate Mode A code as per paragraph 2.2.2.1 should be selected.

May be selected at pilot's discretion.

*0033

Aircraft Paradropping

Unless a discrete Mode A code has already been assigned, pilots of transponder equipped aircraft should select Mode A code 0033, together with Mode C pressure altitude reporting mode of the transponder, five minutes before the drop commences until the drop is complete and parachutists or loads are known or estimated by the pilot to be on the ground.

*0450

Blackpool Basic Service Conspicuity

Aircraft in receipt of a Basic Service from Blackpool Approach.
Shall only be selected with ATC direction.

*1177

London AC (Swanwick) FIS

Aircraft in receipt of a Basic Service from London Information.

Shall only be selected with ATC direction.

*4520

Oxford Approach Basic Service

Aircraft in receipt of a Basic Service from Oxford Approach. Shall only be selected with ATC direction.

*7001

Military Fixed-Wing Low Level Conspicuity and Climb-out

For use by military fixed-wing aircraft on passing 2000 FT MSD in the descent to the UK Low Flying System (LFS) and retained whilst operating in the LFS. When a radar service is required on climb-out from the LFS, the code will be retained until alternative instructions are passed by an ATC Unit.

May be selected at pilot's discretion.

*7002

Danger Areas General

May be selected at pilot's discretion.

*7003

Red Arrows Transit/Display

May be selected at pilot's discretion.

*7004

Aerobatics and Display

For use by civil or military aircraft conducting solo or formation aerobatic manoeuvres, whilst displaying, practising or training for a display or for aerobatics training or general aerobatic practice.

Unless a discrete Mode A code has already been assigned, pilots of transponder equipped aircraft should select *7004, together with Mode C pressure-altitude reporting mode of the transponder, five minutes before commencement of their aerobatic manoeuvres until they cease and resume normal operations.

Pilots are encouraged to contact ATS Units and advise them of the lateral, vertical and temporal limits within which they will be operating and using *7004.

Controllers are reminded that *7004 must be considered as unvalidated and the associated Mode C pressure-altitude reporting data unverified. Traffic information will be passed to aircraft receiving a service as follows:

'Unknown aerobatic traffic, (number) o'clock (distance) miles opposite direction/crossing left/right indicating (altitude) unverified (if Mode C pressure­altitude reporting data is displayed)'.

May be selected at pilot's discretion.

*7005

High-Energy Manoeuvres

Unless a discrete Mode A code has already been assigned, outside controlled airspace below FL 195 and outwith the UK Low Flying System, pilots of military fast-jet aircraft should select *7005 prior to engaging in sustained high-energy manoeuvres. This will highlight to controllers the nature of the flight. Controllers should expect such aircraft to perform sudden and unpredictable changes in altitude and heading, and should be prepared to react accordingly. Controllers are reminded that the *7005 must be considered as unvalidated and the associated Mode C pressure-altitude reporting data unverified.

May be selected at pilot's discretion.

*7006

Autonomous Operations within a TRA and TRA(G)

For use by military aircraft conducting autonomous operations within a TRA or TRA(G).

May be selected at pilot's discretion.

*7010

Operating in an Aerodrome Traffic Pattern

For use by aircraft operating in an aerodrome traffic pattern, when instructed to do so by an ATS Unit or local operating instructions.

Shall only be selected with ATC direction or in accordance with local aerodrome procedures.

*7401

Scottish FIS

Aircraft in receipt of a Basic Service from Scottish Information.

Shall only be selected with ATC direction.

2.2.2.2.2  Pilots are warned of the need for caution when selecting Mode A conspicuity codes in the 70xx series, due to the proximity of the Special Purposes Mode A codes.
2.2.2.2.3  Controllers are reminded that codes annotated with * are used for conspicuity, co-ordination or special purposes and the Mode A and associated Mode C pressure-altitude reporting data must be considered unvalidated and unverified.
2.2.2.2.4 The use of aerodrome-specific conspicuity codes detailed in the UK SSR Code Plan (Table at paragraph 2.6 of ENR 1.6) should be strictly in accordance with local operating instructions/procedures as published by the relevant aerodrome.
2.2.3  Transponder Testing
2.2.3.1 Transponder testing has the potential to generate false SSR returns, thereby incorrectly triggering safety nets such as TCAS and short term conflict alert, with consequential disruption to flight crews and ATC and potential to cause an adverse safety impact. Therefore, individuals or Organisations intending to conduct ground-based transponder testing and maintenance shall take necessary precautions to ensure transponder transmissions cannot be erroneously identified as valid replies by airborne or ground interrogator systems that may detect them. Consequently, the following steps are strongly recommended:
  1. Set the Mode A code to *0002 (UK-specific ground transponder testing code);

  2. Use effective screening or absorption devices on the antennas or physically connect the ramp test set to the antenna system;

  3. Where possible, conduct the testing inside a hangar, as this may provide additional shielding;

  4. Manually set the Mode C pressure-altitude data to either a high value (eg over 60000 FT) or an unrealistically low value (eg 2000 FT below ground);

  5. Select the transponder(s) to 'OFF' or 'STANDBY' when testing is complete.

2.2.3.2 Additional guidance on transponder testing can be found in ICAO Annex 10 Vol IV, JAA TGL 13 and EUROCAE ED-73C.
2.2.4  SSR Site Monitors/Far Field Monitors
2.2.4.1 SSR site monitors, sometimes referred to as Far Field Monitors (FFMs) for Mode S radars, shall use Mode A codes *7776 and *7777, along with Mode C pressure-altitude data set to either a high value (eg over 60000 FT) or an unrealistically low value (eg 2000 FT below ground).
2.2.4.2 Mode S FFMs will also require an ICAO 24-bit address to uniquely identify them. These addresses shall be allocated as part of the National IFF/SSR Committee approval process. For further details contact: nisc@caa.co.uk
2.2.5  Frequency Monitoring Codes
2.2.5.1 In order to both prevent and mitigate the consequences of airspace infringements, pilots operating close to the peripheries of certain controlled airspace and monitoring the relevant frequency (but not requiring an Air Traffic Service) should select a local SSR conspicuity code and the Mode C pressure-altitude mode (if available) as specified to indicate they are monitoring the promulgated ATC frequency. This facility also exists for aircraft routing close to certain airfields outside controlled airspace to advise ATC that pilots are monitoring their frequency.
2.2.5.2 This will allow the appropriate Air Traffic Control Unit to attempt to establish contact with an aircraft which is displaying such a code and which is considered to be infringing, or is likely to infringe, controlled airspace in order to resolve an actual or potential infringement quickly and efficiently. For units outside controlled airspace, this will allow Air Traffic Control to attempt to establish contact with pilots in order to resolve potential conflictions. Selection of such codes does not imply the provision of any form of Air Traffic Service and the use of such codes does not prevent a pilot from requesting an Air Traffic Service at any time should they subsequently decide they require one.
2.2.5.3 In such circumstances, blind transmissions will be made by Air Traffic Control on the appropriate frequency including the code, position, level (if appropriate) and direction of flight of the observed contact. The Mode S-derived callsign may also be used. A pilot monitoring the frequency who suspects, on the basis of the information provided, that theirs is the aircraft being referred to should contact Air Traffic Control accordingly. At this point a discrete code may be assigned to confirm identity. The controller will establish the requirements of the pilot and will confirm the type of Air Traffic Service available. Exceptionally, Air Traffic Control may issue immediate instructions or advice to resolve a particular situation. For aircraft outside controlled airspace, Air Traffic Control may request the pilot’s compliance to achieve coordination. If, after positive identification or on the basis of additional information provided by the pilot it is felt that the aircraft responding is not the aircraft concerned, the pilot will be informed accordingly and may continue to monitor the frequency and if necessary revert to the appropriate monitoring code.
2.2.5.4 Use of monitoring codes does not imply that any form of Air Traffic Service is being provided. The code and any associated Mode C pressure-altitude reporting data is considered to be unvalidated and unverified. Pilots remain responsible for their own navigation and in particular for obtaining permission to enter controlled airspace and Aerodrome Traffic Zones from the appropriate agency.
2.2.5.5 Any pilot who believes they are flying in the vicinity of the aerodromes listed below who is lost or temporarily uncertain of position should immediately seek navigational assistance from the appropriate radar unit. Alternatively, they should select code 0030 and contact London Centre on 121.500 MHz for assistance.
2.2.5.6  Codes in Use
Area/AerodromeSSR CodeRemarks
Aberdeen Airport* 4270This code may be used when flying in the vicinity of Aberdeen Airport and operating outside of the Aberdeen CTR/Aberdeen CTA but within the area defined in EGPD AD 2.22 FLIGHT PROCEDURES.
Belfast Aldergrove* 7045This code may be used when flying in the vicinity of Belfast Aldergrove, within the area defined in EGAA AD 2.22 FLIGHT PROCEDURES.
Belfast City* 4255This code may be used when flying in the vicinity of Belfast/City, within the area defined in EGAC AD 2.22 FLIGHT PROCEDURES.
Birmingham* 0010This code may be used when flying in the vicinity of Birmingham within the area defined in EGBB AD 2.22 FLIGHT PROCEDURES.
Bournemouth* 0011This code may be used when flying in the vicinity of Bournemouth Control Zone and monitoring Bournemouth Radar Frequency within the area defined in EGHH AD 2.22 FLIGHT PROCEDURES. The delineation with Solent is west of a line between Stoney Cross VRP and Hurst Castle VRP.
Bristol* 5077This code may be used when flying in the vicinity of Bristol controlled airspace within the area defined in EGGD AD 2.22 FLIGHT PROCEDURES.
Brize Norton* 3727This code may be used when flying outside of Brize Norton Zone and monitoring Brize Radar Channel 124.280.
Cardiff Airport* 3636This code may be used when flying in the vicinity of Cardiff Airport and operating outside of the Cardiff CTR/Cardiff CTA but within the area defined in EGFF AD 2.22 FLIGHT PROCEDURES.
East Midlands* 4572This code may be used when flying in the vicinity of the East Midlands Control Zones/Areas and monitoring the East Midlands Radar Frequency. Pilots should refer to UK AIP EGNX AD 2.22 FLIGHT PROCEDURES for further details.
Edinburgh* 0440This code may be used when flying in the vicinity of Edinburgh within in the area defined in EGPH AD 2.22 FLIGHT PROCEDURES.
Farnborough* 4572This code may be used when flying in the vicinity of Farnborough; VFR within Class E airspace and VFR or IFR in Class G airspace. Pilots must monitor the LARS West Frequency. All pilots should refer to UK AIP EGLF AD 2.22 FLIGHT PROCEDURES for further details.
Glasgow Airport* 2620This code may be used when flying in the vicinity of Glasgow Airport within the area defined in EGPF AD 2.22 FLIGHT PROCEDURES.
Hawarden* 4607This code may be used when flying in the vicinity of Hawarden within the area defined in EGNR AD 2.22 FLIGHT PROCEDURES.
Leeds Bradford* 2677This code may be used when flying in the vicinity of Leeds Bradford within in the area defined in EGNM AD 2.22 FLIGHTPROCEDURES.
Liverpool* 5060 (5067 for students flying solo)This code may be used when flying in the vicinity of Liverpool and operating outside of the Liverpool CTR/Liverpool CTA but within the area defined in EGGP AD 2.22 FLIGHT PROCEDURES.
London City/ London Heathrow* 0012This code may be used when flying in the vicinity of London City and London Heathrow and operating outside of the London CTR/London City CTR/London CTA but within the area defined in EGLC AD 2.22 FLIGHT PROCEDURES and EGLL AD 2.22 FLIGHT PROCEDURES.
London Gatwick* 7012This code may be used when flying in the vicinity of London Gatwick and operating outside of the London Gatwick CTR/ London Gatwick CTA but within the area defined in EGKK AD 2.22 FLIGHT PROCEDURES.
London Luton CTR/CTA* 0013This code may be used when flying in the vicinity of London Luton and operating outside of the London Luton CTR/ London Luton CTA but within the area defined in EGGW AD 2.22 FLIGHT PROCEDURES.
London Stansted* 7013This code may be used when flying in the vicinity of Stansted and operating outside of the Stansted CTR/Stansted CTA but within the area defined in EGSS AD 2.22 FLIGHT PROCEDURES.
Manchester* 7366 (7367 for students flying solo)This code may be used when flying in the vicinity of Manchester and operating outside of the Manchester CTR/Manchester CTA but within the area defined in EGCC AD 2.22 FLIGHT PROCEDURES.
Newcastle Airport* 3737This code may be used when flying in the vicinity of Newcastle Airport and operating outside of the Newcastle CTR/ Newcastle CTA but within the area defined in EGNT AD 2.22 FLIGHT PROCEDURES.
Norwich Airport* 7350This code may be used when flying in the vicinity of Norwich Airport, operating outside of Norwich CTR/Norwich CTA and monitoring Norwich Radar Frequency 119.355 MHz. Refer to EGSH AD 2.22 FLIGHT PROCEDURES for further details.
Oxford Airport* 4517This code may be used when flying in the vicinity of Oxford Airport and operating outside of the Brize Norton CTR but within the area defined in EGTK AD 2.22 FLIGHT PROCEDURES.
Southampton* 7011This code may be used when flying in the vicinity of Southampton and operating outside of the Southampton CTR/Solent CTA but within the area defined in EGHI AD 2.22 FLIGHT PROCEDURES.
Southend* 5050This code may be used when flying in the vicinity of Southend and operating outside of the Southend CTR/Southend CTA but within the area defined in EGMC AD 2.22 FLIGHT PROCEDURES.
Teesside* 7047This code may be used when flying in the vicinity of Teesside Aerodrome, and operating outside of controlled airspace, but within the area defined in EGNV AD 2.22 FLIGHT PROCEDURES.
Warton Aerodrome* 3660This code may be used when flying in the vicinity of Warton Aerodrome, and operating outside of controlled airspace, but within the area defined in EGNO AD 2.22 FLIGHT PROCEDURES.
2.3  Mode S Aircraft Identification
2.3.1 To comply with ICAO airborne equipment requirements, all Mode S transponder equipped aircraft engaged in international civil aviation must incorporate an Aircraft Identification Feature (sometimes referred to as Flight Identity or Flight ID). Correct setting of Aircraft Identification is essential for the correlation of radar tracks with flight plan data in Air Traffic Management (ATM) and Airport Operator ground systems. Data analysed by the Eurocontrol AMP has shown that many Mode S compliant aircraft are transmitting an incorrect Aircraft Identification, for example, incorrectly setting ABC_123 instead of ABC123.
2.3.2  Incorrect Aircraft Identification settings compromise the safety and ATM benefits of Mode S and will prohibit automatic flight plan correlation, which could affect subsequent ATC clearances and sequencing.
2.3.3 In accordance with ICAO Doc 8168 (PANS-OPS) Vol III, Section 4, Chapter 1, paragraph 1.3, flight crew of aircraft equipped with Mode S having an Aircraft Identification Feature shall set the Aircraft Identification in the transponder. This setting shall correspond to the Aircraft Identification specified in item 7 of the ICAO flight plan, or if no flight plan has been filed, the aircraft registration or as detailed in paragraph 2.3.4.1.
2.3.4 Aircraft Identification, not exceeding 7 alphanumeric characters, is to be entered in item 7 of the flight plan and set in the aircraft as follows:
2.3.4.1 Either,
  1. The ICAO three letter designator (not the IATA two letter designator) for the aircraft operating agency followed by the flight identification, for example, BAW213 or JTR25, when:

    1. In radiotelephony, the callsign used consists of the ICAO telephony designator for the operating agency followed by the flight identification, for example, SPEEDBIRD 213 or HERBIE 25.

    Or,

  2. The registration marking of the aircraft, for example, G-INFO or EIAKO, when:

    1. In radiotelephony, the callsign used comprises the registration marking alone, for example, G-INFO, or is preceded by the ICAO telephony designator for the operating agency, for example, SVENAIR EIAKO;

    2. the aircraft is not equipped with radio.

    Or,

  3. The callsign determined by the military authorities if this will be used to identify the aircraft in radiotelephony during flight.

    Note 1: When the Aircraft Identification consists of less than 7 characters, no zeros, dashes or spaces are to be added, either before or between the characters. Only alphanumeric characters are to be used. Nothing should be added after the final character of the registration. For example, an aircraft registered 'G-INFO' would be input as 'GINFO’.

    Note 2: Appendix 2 to ICAO Doc 4444 (PANS-ATM) refers. ICAO designators and telephony designators for aircraft operating agencies are contained in ICAO Doc 8585.

2.3.5 Flight crew of aircraft which have the capability to change the downlinked aircraft identification feature when airborne shall not change the downlinked aircraft identification feature during the flight unless requested by the air navigation service provider.
2.4  Transponder Failure
2.4.1 Failure before intended departure
2.4.1.1 If the transponder fails before intended departure and cannot be repaired pilots shall:
  1. Plan to proceed as directly as possible to the nearest suitable aerodrome where repair can be made;

  2. inform ATS as soon as possible preferably before the submission of a flight plan. When granting clearance to such aircraft, ATC will take into account the existing and anticipated traffic situation and may have to modify the time of departure, flight level or route of the intended flight;

  3. insert in item 10 of the ICAO flight plan under SSR the letter N for complete unserviceability of the transponder or in the case of partial failure, the letter corresponding to the remaining transponder capability, including unserviceability of any Mode S functionality, as specified in ICAO Doc 4444, Appendix 2.

2.4.2 Failure after departure
2.4.2.1 If the transponder fails after departure or en-route, ATS Units will endeavour to provide for continuation of the flight in accordance with the original flight plan. In certain traffic situations this may not be possible particularly when the failure is detected shortly after take-off. The aircraft may then be required to return to the departure aerodrome or to land at another aerodrome acceptable to the operator and to ATC. After landing, pilots shall make every effort to have the transponder restored to normal operation. If the transponder cannot be repaired then the provisions in paragraph 2.4.1.1 apply.
2.4.3 At present the temporary failure of Mode C alone would not restrict the normal operation of the flight.
2.5  Radio Telephony Phraseology For Use With SSR.

This is in accordance with ICAO Doc 4444, Chapter 12, para 12.4.3.

2.6  UK SSR Code Allocation Plan

(as detailed in the table at ENR 1.6-9 (See also notes below)).

Note 1: Pilots are not to preselect Mode A code settings for discrete codes until instructed to do so by the appropriate controlling agency.

Note 2: The codes or series annotated * are used for conspicuity, co-ordination or special purposes and, unless procedures have been agreed with UK CAA Safety and Airspace Regulation Group, the Mode A code and associated Mode C pressure-altitude reporting data must be considered unvalidated and unverified.

Note 3: These codes are assigned by Aberdeen for helicopters operating in Northern North Sea Off-shore area and out to 5° West.

Note 4: Ground based transponder equipment.

Note 5: This code is allocated to Transit (ORCAM) UK and is temporarily assigned for use by London Control (Swanwick) FIS. Notwithstanding, it retains all the properties and protection of an ORCAM Transit code.

Note 6: These codes will be assigned to aircraft on air policing missions operating under Air Defence Priority Flight (ADPF) status. NATO Air Surveillance and Control System (ASACS) units, NATO Airborne Early Warning aircraft or military ATCCs will normally control the aircraft. The actual controlling unit for a particular flight will be notified by the relevant NATO ASACS unit to the military ATC supervisor whose area of responsibility contains the intended route of the ADPF aircraft. The military ATC supervisor will then inform the relevant civil ATCC. Where any doubt about the controlling agency exists, the relevant military ATC supervisor with the responsibility for the area within which the ADPF aircraft is operating should be contacted in the first instance.

Note 7: This code is assigned by the FISO to aircraft requesting entry into Controlled Airspace for the purpose of joining or crossing the ATS Route network. Pilots shall only select the code when they are within two-way communication with the London FIS. Where available, the Mode C pressure-altitude reporting mode of the transponder should also be selected. If communication is lost or the aircraft leaves the FIS frequency, pilots shall deselect this special purpose code. The assignment of this code does not imply the provision of a radar service and the code and any associated Mode C pressure-altitude reporting data must be considered to be unvalidated and unverified.

Note 8: All Spadeadam squawks indicating flight above FL 50 will be validated and verified by Spadeadam ATC.

Note 9: This conspicuity code shall be used by aircraft operating in an Off-shore Safety Area (OSA) when contact with the Area Air Traffic Service Provider (ATSP) has not been established and no other code has previously been allocated.

Note 10: These codes will be assigned to Unmanned Aeronautical Vehicles operating within an active danger area, which will be validated but may be unverified.

Note 11: Aircraft operating within, and in the vicinity of, EGD123, EGD124, EGD125, EGD126, EGD128.

Note 12: This conspicuity code shall be used by Unmanned Aerial Systems/Remotely Piloted Aircraft that have lost communications with their remote pilot and are following a pre-programmed Lost Link flight profile.

Note 13: This code may also be used for Blackpool Instrument Training.

Note 14: For use within a 20 NM radius of Land’s End up to 4000 FT AMSL.

Note 15: Codes allocated to HQ Air Command are reserved for the purpose of major Operations or Exercises under HQ Air Command control including national events coordinated under HQ 11 Gp.

Note 16: Codes "On loan to CCAMS" may be reallocated to Special Events (e.g. Royal International Air Tattoo) providing at least two weeks' notice is submitted to SSRCodeAllocation@caa.co.uk.

Note 17: The use of the BVLOS UAS/RPA Code does not, in itself, constitute approval to operate Beyond Visual Line of Sight (BVLOS). Operators must ensure they obtain the necessary permissions and approvals from the relevant regulatory authorities prior to conducting any BVLOS operations. When the system is being provided a Flight Information Service or requires positive identification to enable control, a discrete SSR codes from the controlling unit is to be utilised.

Codes / Series

Controlling Authority / Function

* 0000

SSR data unreliable

* 0001

Height Monitoring Unit (See note 4)

* 0002

Ground Transponder Testing (Refer to ENR 1.6, paragraph 2.2.3)

* 0003

Surrey/Sussex HEMS (HLE60)

0004 — 0005

Scottish Non-standard Flights

* 0006

British Transport Police ASU

* 0007

Off-shore Safety Area (OSA) Conspicuity (See note 9)

* 0010

This code may be used when flying in the vicinity of Birmingham, operating outside of Birmingham CTR/ Birmingham CTA and monitoring Birmingham Radar frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 0011

Aircraft operating in the vicinity of Bournemouth Control Zone and monitoring Bournemouth Radar Frequency West (Refer to ENR 1.6, paragraph 2.2.5)

* 0012

This code may be used when flying in the vicinity of London City and London Heathrow and monitoring Thames Director frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 0013

This code may be used when flying in the vicinity of London Luton and monitoring Luton Radar frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 0014

Kent Air Ambulance (HLE21)

* 0015

Essex Air Ambulance (HLE07)

* 0016

Thames Valley Air Ambulance (HLE24)

* 0017

London Air Ambulance (HLE27)

* 0020

Air Ambulance Helicopter Emergency Medivac

* 0021

Fixed-wing aircraft (Receiving service from a ship)

* 0022

Helicopter(s) (Receiving service from a ship)

* 0023

Aircraft engaged in actual SAR Operations

* 0024

Radar Flight Evaluation/Calibration (Refer to ENR 1.6, paragraph 2.2.2.2)

0025

Scottish Non-standard Flights

* 0026

Special Tasks

* 0027

London Control (Swanwick) Ops Crossing/Joining CAS (See note 7)

* 0030

FIR Lost

* 0031

Hertfordshire Air Ambulance (HLE55)

* 0032

Aircraft engaged in police air support operations

* 0033

Aircraft Paradropping (Refer to ENR 1.6, paragraph 2.2.2.2)

* 0034

Antenna trailing/target towing/glider towing

* 0035

Selected Flights - Helicopters

* 0036

Helicopter Pipeline/Powerline Inspection Flights

* 0037

Royal Flights - Helicopters

* 0040

Civil Helicopters North Sea

* 0041 — 0061

Police Air Support

* 0062 — 0076

* 0077

Battlespace Management Force HQ

UAS/RPA Operating Beyond Visual Line of Sight Conspicuity (See note 17)

  
  

* 0100

HQ Air Command (See note 15)

0101 — 0117

Transit (ORCAM) Brussels

0120 — 0137

Transit (ORCAM) Germany

0140 — 0177

Transit (ORCAM) Amsterdam

  
  

* 0200

HQ Air Command (See note 15)

0201 — 0277

Allocated to NATS as CCAMS redundancy

  
  

* 0300

HQ Air Command (See note 15)

0301 — 0377

Assigned by CCAMS

  
  

* 0400

HQ Air Command (See note 15)

* 0401

RAF Leeming Conspicuity

0401 — 0417

Birmingham Radar

0401 — 0437

Ireland Domestic

0401 — 0450

Exeter Approach

0401 — 0461

RAF Lakenheath

0402 — 0437

RAF Leeming

* 0420

Coventry Conspicuity

0421 — 0427

Farnborough Zone/Approach Radar IFR/SVFR

* 0430

Hawarden Airport Conspicuity Code

0430 — 0437

Edinburgh Approach

0430 — 0456

Farnborough LARS West

0431 — 0446

Hawarden Approach

* 0440

This code may be used when flying in the vicinity of Edinburgh, operating outside of Edinburgh CTR/ Edinburgh CTA and monitoring Edinburgh Radar frequency (Refer to ENR 1.6, para 2.2.5)

0441 — 0443

Edinburgh Approach

* 0450

Blackpool Basic Service Conspicuity

* 0451

Blackpool Procedural Service Conspicuity (See note 13)

* 0452

Morecambe Bay Helicopter Conspicuity

* 0453

Liverpool Bay Helicopter Conspicuity

0455

Ekofisk RMZ

* 0457

Farnborough LARS West VFR Conspicuity Code for periods when no discrete SSR code is available

0460 — 0467

Farnborough Zone VFR

* 0462 — 0467USAFE autonomous use in EGD323 complex and Vale of York AIAA.

0470 — 0477

Allocated to NATS as CCAMS redundancy

  
  

* 0500

HQ Air Command (See note 15)

0501 — 0577

Assigned by CCAMS

  
  

* 0600

HQ Air Command (See note 15)

0601 — 0637

Transit (ORCAM) Germany

0640 — 0677

Transit (ORCAM) Paris

  
  

* 0700

HQ Air Command (See note 15)

0701 — 0727

Transit (ORCAM) Maastricht

0730 — 0767

Assigned by CCAMS

0770 — 0777

Transit (ORCAM) Maastricht

Codes / Series

Controlling Authority / Function

1000

IFR GAT flights operating in designated Mode S Airspace

1001 — 1067

Transit (ORCAM) Spain

1070 — 1077

Assigned by CCAMS

  
  

* 1100

HQ Air Command (See note 15)

1101 — 1137

Transit (ORCAM) Germany

1140 — 1176

Assigned by CCAMS

* 1177

London Control (Swanwick) FIS (Refer to ENR 1.6, paragraph 2.2.2.2 and note 5)

  
  

* 1200

HQ Air Command (See note 15)

1201 — 1247

Channel Islands Domestic

1250 — 1257

Assigned by CCAMS

1260 — 1277

Queen Elizabeth Class aircraft carrier operations
  
  
* 1300HQ Air Command (See note 15)

* 1301 — 1306

Assigned by CAA

1307 — 1327

NATO - Air Policing (Air Defence Priority Flights) (See note 6)

1330 — 1377

Transit (ORCAM) Germany

  
  

* 1400

HQ Air Command (See note 15)

1401 — 1407

Irish CCAMS Contingency Codes

1410 — 1477

Assigned by CCAMS

  
  

* 1500

HQ Air Command (See note 15)

* 1501 — 1577

Battlespace Management Force HQ

  
  
* 1600HQ Air Command (See note 15)

* 1601 — 1677

Battlespace Management Force HQ
  
  
* 1700HQ Air Command (See note 15)

* 1701 — 1727

Battlespace Management Force HQ

1730 — 1746

Newquay Approach

1730 — 1746

Farnborough LARS East

* 1730 — 1767

RAF Spadeadam (See note 8)

1730 — 1776

RAF Coningsby

* 1747Farnborough LARS East Conspicuity

* 1747

Newquay Conspicuity

1750 — 1757Farnborough Zone (IFR/SVFR)

1750 — 1756

Newquay Approach

* 1757

Newquay LARS when no discrete SSR code is available

1760 — 1777

RNAS Yeovilton Fighter Control

* 1777

RAF Coningsby Conspicuity

Codes / Series

Controlling Authority / Function

* 2000

Conspicuity when entering United Kingdom airspace from an adjacent region where the operation of transponders has not been required; or when operating within United Kingdom airspace in accordance with IFR and is either not receiving an ATS or has not received a specific instruction from ATS concerning the setting of the transponder; or unless instructed otherwise by ATS, Mode S transponder equipped aircraft on the aerodrome surface when under tow, or parked and prior to selecting Off or STBDY. (Refer to ENR 1.6, paragraphs 2.2.1 e and 2.2.2.1.3)

2001 — 2077

Assigned by CCAMS

  
  

* 2100

HQ Air Command (See note 15)

2101 — 2147

Transit (ORCAM) Amsterdam

2150 — 2177Assigned by CCAMS
  
  

* 2200

HQ Air Command (See note 15)

2201 — 2277

Assigned by CCAMS

  
  

* 2300

HQ Air Command (See note 15)

2301 — 2377

Transit (ORCAM) France

  
  

* 2400

HQ Air Command (See note 15)

* 2401 — 2477

Battlespace Management Force HQ

  
  

* 2500

HQ Air Command (See note 15)

2501 — 2577

Transit (ORCAM) Germany

  
  

* 2600

HQ Air Command (See note 15)

2601 — 2617

Glasgow Approach

2601 — 2637

RAF Cranwell

2601 — 2645

MoD Boscombe Down

2601 — 2657

Irish Domestic Westbound departures and Eastbound arrivals

* 2620

This code may be used when flying in the vicinity of Glasgow, operating outside of Glasgow CTR/ Glasgow CTA and monitoring Glasgow Radar frequency (Refer to ENR 1.6 para 2.2.5)

2621 — 2630

Aberdeen (Sumburgh Approach)

2631 — 2637

Aberdeen (Northern North Sea Off-shore) (See note 3)

2640 — 2642

RAF Cranwell - Lincolnshire AIAA

2640 — 2657

Aberdeen (Northern North Sea Off-shore - Sumburgh Sector) (See note 3)

2643 — 2644

RAF Cranwell

* 2645

RAF Cranwell Conspicuity

2646 — 2647

RAF Cranwell

2646 — 2647

MoD Boscombe Down - UAS

* 2650

MoD Boscombe Down Conspicuity

2650 — 2653

Leeds Bradford Approach

2651 — 2657

MoD Boscombe Down

* 2654

Leeds Bradford Conspicuity

2655 — 2676

Leeds Bradford Approach

* 2660

Thruxton conspicuity

2660 — 2677

Aberdeen (Northern North Sea Off-shore) (See note 3)

2661 — 2675

Middle Wallop

* 2676

Middle Wallop Conspicuity

2677

Middle Wallop Conspicuity

* 2677

This code may be used when flying in the vicinity of Leeds Bradford and monitoring the Leeds Radar Frequency (Refer to ENR 1.6, para 2.2.5)

  
  

* 2700

HQ Air Command (See note 15)

2701 — 2737

Assigned by CCAMS

2740 — 2777

Transit (ORCAM) Zurich

Codes / Series

Controlling Authority / Function

3000

NATO Aircraft receiving a service from AEW aircraft

3001 — 3077

Transit (ORCAM) Zurich

  
  

3100

NATO Aircraft receiving a service from AEW aircraft

3101 — 3127

Transit (ORCAM) Germany

3130 — 3177

Transit (ORCAM) Amsterdam

  
  

3200

NATO Aircraft receiving a service from AEW aircraft

3201 — 3277

Transit (ORCAM) Turkey - may also be Assigned by CCAMS

  
  

3300

NATO Aircraft receiving a service from AEW aircraft

3301 — 3303

Swanwick (Military) Special Tasks

3304 — 3306

Aircraft receiving a service from London D&D Cell

* 3307

D&D Conspicuity Training Fix

3310 — 3367

Swanwick (Military)

3370 — 3377

Allocated to NATS as CCAMS redundancy

  
  

3400

NATO Aircraft receiving a service from AEW aircraft

3401 — 3477

Assigned by CCAMS

  
  

3500

NATO Aircraft receiving a service from AEW aircraft

3501 — 3507

Transit (ORCAM) Luxembourg

3510 — 3537

Assigned by CCAMS

3540 — 3577

Transit (ORCAM) Berlin

  
  

3600

NATO Aircraft receiving a service from AEW aircraft

3601 — 3623

RAF Benson

3601 — 3632

Scottish UK FIS Purposes

3601 — 3634

RAF Waddington

3601 — 3647

Jersey Approach

3601 — 3657

Cardiff Approach

* 3624

RAF Benson Conspicuity

3625 — 3627

RAF Benson

* 3636

This code may be used when flying in the vicinity of Cardiff, operating outside of Cardiff CTR/Cardiff CTA and monitoring Cardiff Approach frequency (Refer to ENR 1.6, para 2.2.5)

* 3637

Wycombe Air Park Conspicuity. Not to be used outside 20 NM from the airfield.

3640 — 3645

RAF Odiham

3640 — 3666

RAF Marham

3640 — 3677

Aberdeen (Northern North Sea Off-shore) (See note 3)

3641 — 3647

BAE Systems Warton

* 3646

RAF Odiham Conspicuity

3646 — 3657

Cardiff Approach

* 3647

3650 — 3653

RAF Odiham Visual Circuit/MATZ Conspicuity when in Contact with Odiham Tower

RAF Odiham

* 3650

BAE Systems Warton Conspicuity

3651 — 3657

BAE Systems Warton

* 3660

This code may be used when flying in the vicinity of Warton Aerodrome and monitoring Warton Radar frequency (Refer to ENR 1.6, para 2.2.5)

3660 — 3665

Solent Approach (Southampton)

3661 — 3677

BAE Systems Warton

* 3666

Solent Radar Conspicuity

* 3667

RAF Marham - FIS Conspicuity

3667 — 3677

Solent Approach (Southampton)

  
  

3700

NATO Aircraft receiving a service from AEW aircraft

3701 — 3706

Norwich Approach

3707Norwich Basic Service
3710Norwich Approach

* 3701 — 3717

Military aircraft under service from RN AEW aircraft in South West Approaches

3701 — 3736

RAF Brize Norton

3701 — 3727

Guernsey Approach

3701 — 3767

RAF Lossiemouth

3720 — 3725

RAF Valley

3720 — 3727

RAF Wittering Approach/Director

3720 — 3766

Newcastle Approach

3726

RAF Valley Basic Service
* 3727This code may be used when flying in the vicinity of RAF Brize Norton, operating outside of Brize Norton CTR and monitoring Brize Norton LARS frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 3727

RAF Valley

3730 — 3736

RAF Valley

3730 — 3747

RAF Wittering Tutor Operations

* 3737

RAF Valley - Visual Recovery

* 3737

RAF Brize Norton Approach Conspicuity

* 3737

This code may be used when flying in the vicinity of Newcastle, operating outside of Newcastle CTR and Newcastle CTA and monitoring Newcastle Radar frequency (Refer to ENR 1.6, para 2.2.5)

3740 — 3745

RAF Brize Norton

3740 — 3747

RAF Valley

* 3750

RAF Wittering Zone Conspicuity (Basic Service)

3750 — 3751

RAF Valley

3750 — 3761

TC Gatwick

3751 — 3757

RAF Wittering Zone Transits

3752

RAF Valley - RIFA

* 3753

RAF Valley - Low Level Helicopters

* 3754

RAF Valley - Special Tasks

3755 — 3756

RAF Valley

3757

RAF Valley Rotary at RAF Mona

3760

RAF Wittering

3760 — 3762

RAF Valley

3761

RAF Wittering – Cranwell/Wittering/Cranwell VFR Transit

* 3762

Shoreham ATS IFR

3762

RAF Wittering

* 3763

Shoreham ATS VFR

3763 — 3765

RAF Valley - Approach/Director

3764 — 3766

Gatwick Tower

3766 — 3767

RAF Valley

* 3767

Redhill Approach Conspicuity

* 3767

Newcastle Approach Conspicuity

3770 — 3777

Western Radar

Codes / Series

Controlling Authority / Function

4000

NATO Aircraft receiving a service from AEW aircraft

4001 — 4077

Transit (ORCAM) France

  
  

4100

NATO Aircraft receiving a service from AEW aircraft

4101 — 4177

Transit (ORCAM) Germany

  
  

4200

NATO Aircraft receiving a service from AEW aircraft

4201 — 4210 Western Radar

4211 — 4214

Assigned by CAA

4215 — 4247

Assigned by CCAMS

4250 — 4257

Belfast City Approach

4250 — 4267

Aberdeen Approach

4250 — 4277

Humberside Approach

* 4255

This code may be used when flying in the vicinity of Belfast/City, operating outside of Belfast/City CTR/ Belfast TMA and monitoring Belfast Approach frequency (Refer to ENR 1.6, para 2.2.5)

* 4270This code may be used when flying in the vicinity of Aberdeen Airport and operating outside of the Aberdeen CTR/Aberdeen CTA (Refer to ENR 1.6, para 2.2.5)
  

4300

NATO Aircraft receiving a service from AEW aircraft

4301 — 4305

Assigned by CAA

* 4306

Lee-on-Solent Conspicuity

4307 — 4317

London Control Non-Standard Flights

4320 — 4327

Ireland Domestic

4320 — 4327

RNAS Yeovilton

4330 — 4337

UK Domestic (Prestwick Centre Special Sector Codes)

4340 — 4353

UK Domestic (Scottish Special Sector Codes)

* 4354 — 4356

Westland Helicopters Yeovil

4357

Ireland Domestic

* 4357RNAS Yeovilton Conspicuity

4360 — 4361

Oil Survey Helicopters - Faeroes/Iceland Gap

* 4360 — 4367

Westland Helicopters Yeovil

4360 — 4367

RAF Northolt

4370 — 4377

Anglia Radar

4370 — 4377

Ireland Domestic

4370 — 4377

RNAS Yeovilton

  
  

4400

NATO Aircraft receiving a service from AEW aircraft

4401 — 4427

Transit (ORCAM) Brussels

4430 — 4477

Assigned by CCAMS

  
  

4500

NATO Aircraft receiving a service from AEW aircraft

* 4501

Land’s End GNSS Approach (See note 14)

* 4501

Wattisham Conspicuity

4501 — 4516

Oxford Approach

4501 — 4517

Prestwick Approach

4502 — 4547

Wattisham Approach

4506RAF Topcliffe

* 4517

This code may be used when flying in the vicinity of Oxford Airport and monitoring Oxford Radar frequency (Refer to ENR 1.6, para 2.2.5)

* 4520

Prestwick Conspicuity

* 4520

Oxford Approach Basic Service

* 4521 — 4527

West Wales Radar (NQY)

* 4530

MoD Aberporth Conspicuity

* 4530

Gloucestershire Airport Instrument Approach Training

4530 — 4546

Plymouth (Military) Radar

4531 — 4537

MoD Aberporth

* 4531

Gloucestershire Airport Conspicuity only to be used within 25 NM and 10,000 FT of the airfield and monitoring the Gloucestershire Airport Frequency

* 4540 — 4542

MoD Aberporth (See note 10)

* 4540 — 4541RAF Topcliffe Conspicuity Code

* 4543

West Wales Airport UAS Conspicuity Code. Shall only be selected with AFIS direction.

* 4547

Plymouth (Military) Radar conspicuity

4550 — 4567

Plymouth (Military) Radar

4550 — 4567

Isle of Man

4550 — 4570

East Midlands Radar

* 4571

East Midlands LARS Basic Service Conspicuity

* 4572

Aircraft operating outside of East Midlands Controlled Airspace/Zone and monitoring East Midlands Radar frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 4572

Farnborough LARS West VFR Frequency Monitoring Code (Refer to ENR 1.6, paragraph 2.2.5)

* 4573

Costock Helicopters operating inside East Midlands CTR - Conspicuity

* 4574

Southdown Gliding Club Conspicuity

* 4575

Southend Airport Conspicuity

* 4575

Haverfordwest RNP Approach Conspicuity. Only to be used within 20 NM and 10,000 FT of the aerodrome

* 4576Walney Aerodrome Conspicuity. Only to be used within 25 NM and 10,000 FT of the aerodrome and in
communication with Walney ATS.

* 4576

RAF Honington

* 4577

Allocated by the CAA

  
  

4600

NATO Aircraft receiving a service from AEW aircraft

* 4601

MoD Ops in Salisbury Plain Training Area (See note 11)

4602 — 4607

Anglia Radar

* 4607

This code may be used when flying in the vicinity of Hawarden and monitoring the Hawarden Radar Frequency (Refer to ENR 1.6 para 2.2.5)

4610 — 4667

Assigned by CCAMS

4670 — 4676

TC Stansted/TC Luton

* 4677

Luton Airport Tower Conspicuity

  
  

4700

NATO Aircraft receiving a service from AEW aircraft

4701 — 4777

Assigned by CCAMS

Codes / Series

Controlling Authority / Function

5000

NATO Aircraft receiving a service from AEW aircraft

5001 — 5012

London Control Non-Standard Flights

5013 — 5017

Assigned by CCAMS

5020 — 5036

Farnborough LARS North

* 5037Farnborough LARS North Conspicuity

5040 — 5047

Assigned by CAA

* 5050

Liverpool Conspicuity

* 5050

This code may be used when flying in the vicinity of Southend and monitoring Southend Radar Frequency (Refer to ENR 1.6, para 2.2.5)

5050 — 5067

Bristol Approach

5050 — 5067

Southend Approach

5051 — 5067

Liverpool Airport

* 5060 (or 5067 for students flying solo)

This code may be used when flying in the vicinity of Liverpool and monitoring the Liverpool Radar Frequency (Refer to ENR 1.6, para 2.2.5)

* 5070 — 5071

Bristol VFR Conspicuity

* 5070 — 5071

RAF Syerston Conspicuity

5072 — 5076

Bristol Approach

* 5077

This code may be used when flying in the vicinity of Bristol Airport, operating outside of Bristol CTR/ Bristol CTA and monitoring Bristol Radar frequency (Refer to ENR 1.6, para 2.2.5)

* 5077

Sherburn-in-Elmet and Leeds East RNP Approach Conspicuity. Only to be used within 20 NM and 10,000 FT of the aerodrome

* 5077

Cumbernauld RNP Approach Conspicuity. Only to be used within 20 NM and 10,000 FT of the aerodrome

 
  

5100

NATO Aircraft receiving a service from AEW aircraft

5101 — 5107

Assigned by CAA

5110 — 5137

NATS

5140 — 5177

Assigned by CCAMS
  
  

5200

NATO Aircraft receiving a service from AEW aircraft

5201 — 5270

Assigned by CCAMS

5271 — 5277

Transit (ORCAM) Channel Islands

  
  

5300

NATO Aircraft receiving a service from AEW aircraft

5301 — 5377

Transit (ORCAM) Barcelona

  
  

5400

NATO Aircraft receiving a service from AEW aircraft

5401 — 5477

Assigned by CCAMS

  
  

5500

NATO Aircraft receiving a service from AEW aircraft

5501 — 5577

Transit (ORCAM) Barcelona

  
  

5600

NATO Aircraft receiving a service from AEW aircraft

5601 — 5647

Transit (ORCAM) Paris

5650 — 5657

Transit (ORCAM) Luxembourg

5660 — 5664

Allocated to NATS as CCAMS redundancy

5665 — 5676

Assigned by CCAMS

5677Medical emergency in France
  
  

5700

NATO Aircraft receiving a service from AEW aircraft

5701 — 5777

Transit (ORCAM) Geneva

Codes / Series

Controlling Authority / Function

* 6000

HQ Air Command (See note 15)

* 6001 — 6037

On loan to CCAMS (See note 16)

6040 — 6077

Swanwick (Military)

  
  

* 6100

HQ Air Command (See note 15)

6101 — 6157

Swanwick (Military)

6160 — 6175

Cambridge Approach

6160 — 6176

Inverness Radar

6160 — 6177

Plymouth (Military) Radar

6161 — 6167

Doncaster Sheffield (CAA Reserved)

6171 — 6177

Doncaster Sheffield (CAA Reserved)

* 6176

Cambridge VFR Conspicuity

* 6177

Cambridge IFR Conspicuity

* 6177

Inverness Conspicuity

  
  

* 6200

HQ Air Command (See note 15)

6201 — 6257

Assigned by CCAMS

6260 — 6277

Transit (ORCAM) Amsterdam

  
  

* 6300

HQ Air Command (See note 15)

6301 — 6377

Assigned by CCAMS

  
  

* 6400

HQ Air Command (See note 15)

6401 — 6457

Swanwick (Military) Radar

6460 — 6467

Assigned by CCAMS

6470 — 6477

Allocated to NATS as CCAMS redundancy

  
  

* 6500

HQ Air Command (See note 15)

6501 — 6577

CRC Boulmer
  
  

* 6600

HQ Air Command (See note 15)

6601 — 6677

Transit (ORCAM) Germany

  
  

* 6700

HQ Air Command (See note 15)

6701 — 6777

Transit (ORCAM) France

Codes / Series

Controlling Authority / Function

* 7000

Conspicuity when operating within United Kingdom airspace in accordance with VFR and have not received a specific instruction from ATS concerning the setting of the transponder. (Refer to ENR 1.6, paragraph 2.2.2.1.3)

* 7001

Military Fixed-wing Low Level Conspicuity/ Climb-out (Refer to ENR 1.6, paragraph 2.2.2.2)

* 7002

Danger Areas General

* 7003

Red Arrows Transit/Display

* 7004

Conspicuity Aerobatics and Display (Refer to ENR 1.6, paragraph 2.2.2.2)

* 7005

High-Energy Manoeuvres

* 7006

Autonomous Operations within TRA and TRA (G) (Refer to ENR 1.6, paragraph 2.2.2.2)

7007

Open Skies Observation Aircraft

* 7010

Operating in Aerodrome Traffic Pattern (Refer to ENR 1.6, paragraph 2.2.2.2)

* 7011

This code may be used when flying in the vicinity of Southampton Airport and monitoring Solent Radar frequency (Refer to ENR 1.6, paragraph 2.2.5)

* 7012

This code may be used when flying in the vicinity of London Gatwick and monitoring Gatwick Director frequency (Refer to ENR 1.6, para 2.2.5)

* 7013

This code may be used when flying in the vicinity of Stansted and monitoring Stansted Radar frequency (Refer to ENR 1.6, para 2.2.5)

7014 — 7017

Allocated to NATS as CCAMS redundancy

7020 — 7027

Assigned by CCAMS

* 7030

RNAS Culdrose Conspicuity

7030 — 7044

Aldergrove Approach

7030 — 7046

TC Thames/TC Heathrow

7030 — 7046

Teesside International Airport

7030 — 7077

Aberdeen (Northern North Sea Off-shore) (See note 3)

7031 — 7077

RNAS Culdrose

* 7045

This code may be used when flying in the vicinity of Belfast Aldergrove, operating outside of Belfast Aldergrove CTR/Belfast TMA and monitoring Aldergrove Approach frequency (Refer to ENR 1.6, para 2.2.5)

7046 — 7047

Aldergrove Approach

* 7047

* 7047

TC Thames (Biggin Hill Airport Conspicuity)
This code may be used when flying in the vicinity of Teesside, operating outside of Teesside CTR and Teesside CTA and monitoring Teesside Radar frequency (Refer to ENR 1.6, para 2.2.5)

* 7047

RNAS Culdrose Conspicuity

7050 — 7056
7050 — 7066

TC Thames/TC Heathrow
Teesside International Airport

* 7057

TC Thames (London City Airport Conspicuity)

* 7066

Lydd Approach VFR

* 7067

Teesside International Airport Conspicuity

* 7067

Lydd Approach IFR

7070 — 7076

TC Thames/TC Heathrow

* 7077

TC Thames (London Heliport Conspicuity)

  
  

* 7100

SSR Code Saturation

7101 — 7167

Transit (ORCAM) Brussels

7170 — 7177Transit (ORCAM) Luxembourg
  
  

* 7200

RN Ships Conspicuity

7201 — 7267

Allocated to NATS as CCAMS redundancy

7270 — 7277

Assigned by CCAMS

  
  

* 7300

MPA/DEFRA/Fishery Protection/AIRTASK146

* 7300

(Civil Contingency) Conspicuity

7301 — 7327

Assigned by CCAMS

7330 — 7347

Transit (ORCAM) Netherlands

* 7350

Norwich Frequency Monitoring Code - This code may be used when flying in the vicinity of Norwich, operating outside of Norwich CTR/Norwich CTA and monitoring Norwich Radar Frequency (Refer to ENR 1.6, paragraph 2.2.5)

7350 — 7353

RNAS Culdrose

7350 — 7361

MoD Ops in EGD701 (Hebrides)

7350 — 7363

Manchester Approach

7350 — 7376

Bournemouth Approach/LARS

7351 — 7377

Norwich Approach

* 7354 — *7355

RNAS Culdrose Conspicuity

* 7356RNAS Culdrose Conspicuity Code utilised by Penzance Heliport iaw local orders
* 7357RNAS Culdrose Conspicuity

7360 — 7367

RNAS Culdrose

* 7362

MoD Ops in EGD702 (Fort George)

* 7365

Manchester Barton Conspicuity

* 7366 (or 7367 for students flying solo)

This code may be used when flying in the vicinity of Manchester Airport and monitoring Manchester Radar frequency (Refer to ENR 1.6, paragraph 2.2.5)

7367 — 7373

Manchester Approach

* 7374

Dundee Airport IFR Procedural Approach

* 7375

Manchester TMA and Woodvale Local Area (Woodvale UAS and VGS Conspicuity)

* 7376

Dundee Airport VFR Conspicuity

* 7377

Bournemouth Radar Conspicuity

  
  

* 7400

UAS/RPA Lost Link (See note 12)

* 7401

Scottish FIS (Refer to ENR 1.6, paragraph 2.2.2.2)

* 7402

RAF Leuchars Conspicuity

7402 — 7414

TC Stansted/TC Luton

7402 — 7417

RAF Shawbury

7402 — 7436

RNAS Yeovilton

7402 — 7437

Anglia Radar

7403 — 7427

RAF Leuchars

* 7417

Cranfield Airport - IFR Conspicuity Purposes

* 7420

RAF Shawbury Conspicuity

7421 — 7425

RAF Shawbury

* 7426

RAF Shawbury Conspicuity

* 7427

RAF Shawbury

7430 — 7437RAF Shawbury

* 7437

RNAS Yeovilton Conspicuity

7440 — 7477

Transit (ORCAM) France

  
  

* 7500

Special Purpose Code - Hi-Jacking

7501 — 7507

Assigned by CCAMS

7510 — 7535

Transit (ORCAM) Switzerland

7536 — 7537

Assigned by CCAMS

7540 — 7547

Transit (ORCAM) Germany

7550 — 7567

Transit (ORCAM) Paris

7570 — 7577

Assigned by CCAMS

  
  

* 7600

* 7601

Special Purpose Code - Radio Failure

Special Purpose Code - European Radio Failure Procedure (Not Avaliable in UK FIR)

7602 — 7617

Allocated to NATS as CCAMS Redundancy (Prestwick Upper)

7620 — 7677

Assigned by CCAMS

  
  

* 7700

Special Purpose Code - Emergency

7701 — 7775

Assigned by CCAMS

* 7776 — 7777

SSR Monitors (Refer to ENR 1.6, paragraph 2.2.4)

2.7  Centralised Code Assignment and Management System (CCAMS)
2.7.1 The UK is part of the Centralised Code Assignment and Management System (CCAMS). CCAMS optimises the efficiency of European SSR code management by centrally selecting a SSR Mode A code for each flight based on its area of applicability and distributing it to the appropriate ATS unit. The Originating Region Code Assignment Method (ORCAM) will continue to be used by those nations which are not participating in CCAMS for international flights. For participating nations CCAMS will allocate ORCAM compatible codes.
2.7.2 To mitigate against the risk of CCAMS failure or in the event of a potential confliction with a CCAMS allocated code, states are allocated blocks of codes that can be used in place of CCAMS if necessary. In the UK, these blocks of codes are managed by NATS and are articulated in Section 2.6 as “Allocated to NATS as CCAMS redundancy”.
3  Automatic Dependent Surveillance - Broadcast (ADS-B)
3.1 Commission Regulation (EU) No. 1207/2011, as amended, requires aircraft with a maximum certified take-off mass exceeding 5,700 KG or having a maximum cruising true airspeed capability greater than 250 KT, operating as GAT under IFR, to be equipped with ADS-B version 2, typically pairing of a 1090 MHz Mode S “Extended Squitter” (ES) Level 2 transponder with an approved GNSS navigation source to provide the required data items as per Annex II Part B of that regulation. This applies to transport-type State aircraft (military, customs or police fixed-wing aircraft operated for the purpose of transporting persons and/or cargo) unless notified to the UK CAA.
3.2 Aircraft that are unable to transmit ADS-B for technical or operational reasons will be accommodated by UK ANSPs through conventional surveillance e.g. Mode S. See section GEN 1.5.3.
3.3 The UK’s preferred national system to improve electronic conspicuity for general aviation is ADS-B using 1090 MHz. It is also likely that ADS-B will become more prevalent as a source of surveillance data for all aircraft types and to providers of ATS.
3.4 Extended Squitter devices using uncertified GPS sources may require the Surveillance Integrity Level to be set to zero.
4  Other Relevant Information and Procedures
4.1  Lower Airspace Radar Service (LARS)
4.1.1  Availability of Service
4.1.1.1 The service is available to all aircraft flying outside Controlled Airspace up to FL 100, within the limits of radar/radio cover. The service will be provided within approximately 30 NM of each participating ATS Unit. Unless a participating ATS Unit is H24, the service will normally be available between Winter 0800 and 1700, Summer 0700 and 1600, Mondays to Fridays. However, as some participating Units may remain open to serve evening, night or weekend flying, pilots are recommended to call for the service irrespective of the published hours of ATS. If no reply is received after three consecutive calls, it should be assumed that the service is not available.
4.1.1.2 LARS will not normally be available from non-H24 Units at weekends and during public holidays.
4.1.1.3 Pilots intending to operate at or above FL 100 may be advised to contact an appropriate ATCRU and request a Deconfliction Service or a Traffic Service. However, as VHF frequencies at Military ATCRUs are not continuously monitored, unless in use, civil pilots may ask controllers to arrange a frequency on which to call the appropriate Unit.
4.1.2  Description of Service
4.1.2.1 The service provided will be a Deconfliction Service or Traffic Service as detailed at ENR 1.1, subsection 2 (UK Flight Information Service).
4.1.3  Procedures
4.1.3.1 Pilots intending to use the Lower Airspace Radar Service should note the participating ATS Units close to their intended track and establish two-way RTF communication on the appropriate frequency using the phraseology: '. . . . .(Participating ATS Unit), . . . . .(Aircraft callsign), request (Basic/Traffic/Deconfliction Service)'. Pilots may be asked to 'stand-by'. When asked to pass your message, pilots should pass the following information:
  1. Callsign and type of aircraft;

  2. departure aerodrome;

  3. destination aerodrome;

  4. present position;

  5. level;

  6. additional details/intentions as necessary (next route point, squawk code).

4.1.3.2 Aircraft will be identified and pilots so informed before radar service is given.
4.1.3.3 Under a Deconfliction Service or Traffic Service, participating LARS aircraft will be given the service in accordance with ENR 1.1, subsection 2 (UK Flight Information Service).
4.1.3.4 Whenever possible, aircraft will be handed over from controller to controller in an area of overlapping radar cover and pilots told to 'Contact' the next Unit. When this cannot be effected, pilots will be informed of their position and advised which Unit to call for further service.
4.1.3.5 If a pilot wishes to enter regulated airspace, even though he may be in receipt of a LARS beforehand, he remains responsible for obtaining the required clearances before entry. LARS Controllers may assist in obtaining clearance, if workload permits, but pilots must be prepared to carry out this task independently.
4.1.4  Terrain Clearance
4.1.4.1 Terrain clearance will be the responsibility of pilots. However, LARS Units will set a level or levels below which a Deconfliction Service is to be refused or terminated.
4.1.5  Advice to Pilots
4.1.5.1 The provision of LARS is at the discretion of the controllers concerned because they may be fully engaged in their primary tasks. Therefore, occasionally, the service may not be available.
4.1.5.2 Boscombe Down Service Limitations
4.1.5.2.1 Limited Traffic Service - At and below FL 40. Subject to ATC workload, pilots will be informed of any limitations to Deconfliction Service and standard separation will be provided whenever possible.
4.1.5.3 Cardiff Radar Service Limitations
4.1.5.3.1 Due to limits of surveillance cover, a LARS may not be available below altitude 3000 FT. Pilots will be advised if LARS is not available and an alternative ATS may be offered.
4.1.5.4 Farnborough Service Limitations
4.1.5.4.1 Limited Traffic Service - At all altitudes/Flight Levels. Aircraft inbound to Farnborough should contact Farnborough Radar on 134.355 MHz. On weekdays (excluding PHs) LARS/MATZ service is not normally available on 125.250 MHz after 2000 HR (one hour earlier in summer). Traffic inbound to Odiham should contact Odiham Approach on 131.305.
4.1.5.4.2  Traffic Service is not available below altitude 1500 FT.
4.1.5.5  Warton Service Limitations
4.1.5.5.1  Warton PSR is suppressed in certain sectors to mitigate interference from ground clutter and wind turbines. Pilots will be advised of reduced service by Warton Radar.
4.1.6  ATS Units Participating in the Lower Airspace Radar

Unit

Position

Frequency

(MHz)/Channel

Service Radius

(NM)

Availability/ Remarks

Boscombe Down

510912N 0014504W

126.705

30

Mon-Thu 0900-1700 (0800-1600), Fri 0900-1600 (0800-1500).
Opening hours may vary subject to operational flying requirements.

Bournemouth

504648N 0015033W

119.480

30

0800-2000 (0700-1900).

Brize Norton

514500N 0013459W

124.280

40

0900-1700 (0800-1600).

Cardiff

512348N 0032036W

119.155

40

0600-2300 (0500-2200).

Coningsby

530535N 0000958W

119.205

30

Mon-Fri 0800-1700 (0700-1600).

Culdrose

500507N 0051515W

134.055

30

Mon-Thu 0830-1700 (0730-1600), Fri 0830-1400 (0730-1300).

East Midlands

524952N 0011940W

134.180

30

H24.

Exeter

504404N 0032450W

128.980

30

Mon-Fri 0630-0230 (0500-0200), Sat 0600-2100 (0500-0200), Sun 0600-2200 (0500-0200).

Farnborough (West)

511633N 0004635W

125.250

See ENR 6-11

0800-2000 (0700-1900).
See paragraph 4.1.7.

Farnborough (East)

511633N 0004635W

123.225

Farnborough (North)

511633N 0004635W

132.800

Humberside

533428N 0002103W

119.130

30

0630-2115 (0530-2015).

Leeming

541733N 0013207W

133.380

30

Mon-Thu 0800-1800 (0700-1700), Fri 0800-1700 (0700-1600).

Leuchars

562230N 0025132W

126.505

40

Mon-Fri 0900-1700 (0800-1600).

Lossiemouth

574224N 0032016W

119.575

40

Mon-Fri 0900-1700 (0800-1600).

Marham

523854N 0003302E

124.155

30

Mon-Thu 0800-2359 (0700-2300), Fri 0800-1800 (0700-1700).

Newcastle

550217N 0014123W

124.380

40

H24.

Newquay

502627N 0045943W

133.405

60

0730-2130 (0630-2030).

Norwich

524033N 0011658E

119.355

30

0630-2130 (0530-2030).

Plymouth Military (West)

501900N 0040700W

121.255

40

Mon-Thu 0800-1700 (0700-1600), Fri 0800-1400 (0700-1300).

Plymouth Military (East)

503405N 0022659W

124.150

40

The East and West LARS areas are divided at the western edge of Berry Head CTA 1, 3 & 5.

Shawbury

524737N 0024005W

133.155

40

Mon-Fri 0830-1700 (0730-1630).

Southend

513417N 0004144E

130.780

25

0900-1800 (0800-1700).

Teesside International

543033N 0012546W

118.855

40

0800-1800 (0700-1700).

Valley

531450N 0043201W

125.230

40

Mon-Thu 0800-1800 (0700-1700), Fri 0800-1700 (0700-1600).

Waddington

530958N 0003126W

119.505

30

Mon-Thu 0800-1800 (0700-1700), Fri 0800-1300 (0700-1200).

Warton

534442N 0025300W

129.530

40

Mon-Thu 0730-1900 (0630-1800), Fri 0730-1700 (0630-1600).

Yeovilton

510030N 0023844W

127.355

30

Mon-Thu 0830-1600; Fri 0830-1300.

4.1.7  Farnborough LARS
4.1.7.1 The co-ordinates of the Farnborough Radar Sectors are detailed below. The boundaries shown purely indicate the extent of the available service and DOES NOT infer that Farnborough LARS will be the controlling Authority for the crossing of either CAS or Military ATZs.
  1. LARS North

    520742N 0001825W - 520729N 0000708W - 520755N 0000723E - 520457N 0002608E - 520157N 0003808E - 515031N 0004700E – 514654N 0003118E – 513759N 0001801E – 513421N 0001707E – 513534N 0001246E – 513612N 0002639W - 513611N 0004133W - 514401N 0010541W thence clockwise by the arc of a circle radius 30 NM centred on 511631N 0004639W (Farnborough ARP) to 514550N 0005638W - 515411N 0004452W - 520742N 0001825W.

  2. LARS East

    511814N 0003550E - 505613N 0003110E - 504354N 0001455E - 504325N 0003247W - 504846N 0003247W - 510054N 0002700W - 511030N 0002352W thence clockwise by the arc of a circle radius 8 NM centred on 510853N 0001125W to 511118N 0002332W - 511242N 0001323W - 512013N 0001255W - 513611N 0001253W - 513534N 0001246E – 513421N 0001707E – 511833N 0002531E - 511814N 0003550E

  3. LARS West

    514401N 0010541W - 513611N 0004133W - 513612N 0002639W - 513611N 0001253W - 512013N 0001255W - 511242N 0001323W - 511118N 0002332W thence an arc radius 8 NM centred on 510853N 0001125W to 511030N 0002352W - 510054N 0002700W - 504846N 0003247W - 504325N 0003247W - 504313N 0004727W - 504957N 0010837W thence an arc 30 NM radius centred on 511631N 0004639W (Farnborough ARP) to 514401N 0010541W.

4.2  Radar Service - FL 100 and Above (Outside CAS)
4.2.1  Availability of Service
4.2.1.1 This service is available to all aircraft flying outside CAS in the London and Scottish FIRs between FL 100 and FL 190, and within active TRAs, subject to Unit capacity.
4.2.1.2 The military Units providing this service together with their boundaries are depicted on the chart at ENR 6-12. The table below shows their hours of operation, the RTF operating frequency on which this service is normally provided and a telephone number for pre-flight contact.

Unit and Callsign

Operating Hours

Initial Contact Frequency (ICF)

Telephone Number

78 Squadron Swanwick (Swanwick Mil)

H24 (Subject to 4.2.3)

North West Sector 134.300 MHz,
North Sector 136.375 MHz,
North East Sector 135.075 MHz,
East Sector 133.325 MHz,
Central Sector 128.700 MHz,
West Sector (Northern) 127.450 MHz,
West Sector (Southern) 133.900 MHz &
South West Sector 135.150 MHz.

01489-612943

01489-612408

01489-612417

Western Radar

0645-1930 (0545-1830)

132.300 MHz

Admin: 01489-585511

4.2.1.3 Participating aircraft must be equipped with a serviceable transponder.
4.2.2  Type of Service
4.2.2.1 The service provided will be a Deconfliction Service or Traffic Service (See ENR 1.1.2).
4.2.3  Availibility of Service
4.2.3.1 Swanwick (Mil) will only provide an ATS 2300-0700 (2200-0600) Mon to Thu, and 2300-0700 (2200-0600) Fri to Mon subject to 2 weeks notification and associated approval. A request is to be sent to: SWK-Plans@mod.gov.uk and contain the details laid out in 4.2.4.1 (b). Swanwick (Mil) also have reduced staffing between the hours of 1800-2300 (1700-2200) Mon to Fri, provision of service will be prioritised in accordance with RAF Battlespace Management Orders.
4.2.4  Procedures
4.2.4.1 In order to comply with the requirements of the FPPS at 78 Squadron (Swanwick Mil), captains of aircraft requiring a radar service in the Upper or Lower Airspace within the Swanwick(Mil) area of responsibility are to pre-notify their intended flight details to Swanwick(Mil) by one of the following methods:
  1. Pre-flight Notification - Flight Plans. As the preferred method of notification flight plans (F2919/CA48) should be submitted as far in advance of ETD as possible and in any case not less than 30 minutes before service is required. The Swanwick(Mil) signals address - EGZYOATT - must be included on the flight plan. When appropriate these additions to the standard flight plan format must also be included:

    1. Item 18. The point and the time at which a radar service is required to commence;

    2. Item 15. The point of entry into the area and the point of exit.

      Note: Item 15. If a flight is planned to enter any CAS within the Swanwick(Mil) area of responsibility and a service is required before joining or after leaving CAS, both parts of the route may be entered in Item 15 of the same flight plan. In this case both IFPS - EGZYIFPS - and Swanwick(Mil) EGZYOATT must appear as addressees.

  2. Pre-Flight Notification - Military Prenote. When it has not been possible to file a flight plan, as sub-paragraph (a), relevant details of the intended flight should be telephoned by the pilot or by his aerodrome operations or ATC to Swanwick(Mil), Main Flight Plan Reception Section, (ATOTN Telephone Ext 6710) at least 15 minutes before service is required. Flight details should be passed in this order:

    1. Callsign;

    2. number of aircraft (if more than 1) and aircraft type(s);

    3. position and time at which service is required to commence;

    4. speed and flight level at commencement of service;

    5. route (including any required speed or level changes);

    6. position of leaving the delineated area (if applicable); and

    7. destination (ICAO Location Indicator).

  3. In-Flight Notification (Air Filing). Exceptionally, when neither form of pre-flight notification has been made the flight details listed in sub-paragraph (b) above, may be notified in flight (Air Filed) by radio to:

    1. ATCRU. Airfile with the ATCRU, currently providing a service for onward transmission by them to Swanwick(Mil) at least 15 minutes in advance of service being required;

    2. Swanwick(Mil). Request radar service by calling Swanwick(Mil) on the appropriate (ICF), at least 5 minutes before service is required passing the details listed in sub-paragraph (b) above.

  4. In order to comply with the requirements of the FPPS for Western Radar, pilots and operators of aircraft leaving or joining Controlled Airspace within the Western Radar Area of Operation, who wish to receive an ATS from Western Radar are advised to file all flight plans (CA48) to both EUCHZMFP and EUCBZMFP not less than 30 minutes before the ATS is required.

    The flight plan should include the following information:

    1. Item 18. The point and time at which a UK FIS radar service will be required within the Western Radar Area of Operation.

    2. Item 15. The point of entry into and exit from the Western Radar Area of Operation.

      Note: An ATS is available to aircraft entering or leaving CAS within the Western Radar Area of Operation; therefore, to secure an ATS, Flight Plan Item 15 is to be fully completed.

4.2.4.1.1 Changes to Flight Details
  1. Pre-Flight Notification. Changes to pre-flight notifications are to be passed to Swanwick(Mil) as soon as possible by:

    1. Amended flight plan if time permits (as in paragraph 4.2.3.1 (a)); otherwise

    2. by telephone (as in paragraph 4.2.3.1 (b)).

  2. In-Flight Notification (Air Filing). By RTF as soon as possible (as in paragraph 4.2.3.1 (c)).

4.3  (Former) Pennine Radar Area of Responsibility
4.3.1  Area of Responsibility
4.3.1.1 Provision of ATS outside of controlled airspace within the area defined below is a NATS licensed task which is provided, subject to unit workload, by Swanwick(Mil):
  1. 550000N 0015420W - 550000N 004444W - 534153N 0002245E - 534134N 0010443W - 534007N 0011937W - 535348N 0013100W - 535955N 0014027W - 540236N 0014900W - 535557N 0020827W - 541113N 0021858W - 541201N 0021700W - 545127N 0023916W - 550000N 0015420W.

  2. But excluding:

    1. Aerodrome Traffic Zones (ATZ);

    2. Danger Areas;

    3. Newcastle CTR/CTA;

    4. Teesside International CTR/CTA

4.3.1.2 Vertical limits between FL 55 and FL 195. Deconfliction Service will not be provided below 4000 FT Regional Pressure Setting (RPS). Exceptionally, a Traffic Service may be provided below 4000 FT RPS, however, radar vectors will not be provided. (If there are high traffic levels in the Vale of York AIAA this may preclude standard separation from being maintained and a Traffic Service or a re-route may be offered).
4.3.1.3 Core operating hours are Mon-Fri 0700-2030 (Summer 1hr earlier). However, outside of these hours a service may still be provided H24 subject to unit capacity.
4.3.1.4 The area of responsibility is depicted on chart ENR 6-14.
4.3.1.5 Other ATSUs providing a radar service, within the Area of Responsibility, are:
  1. Lower Airspace Radar Service (LARS) areas of Warton, Teesside International, Newcastle, Leeming and Humberside;

  2. Anglia Radar Area of Responsibility (ENR 6-25).

4.3.2  Flight Plan Requirements
4.3.2.1 Pilots wishing to receive an ATS from Swanwick(Mil) within the Former Pennine Radar Area are to include within their Flight Plan the Swanwick(Mil) address EGZYOATT, in addition to any other IFPS address requirements. This requirement also applies to aircraft wishing to join or leave L602 at ERKIT routing in or outbound from EGNT or EGNV. Failure to address Flight Plans to Swanwick(Mil) may result in the refusal of service.
4.3.3  Radio Communication
4.3.3.1 Pilots receiving a service who wish to leave the frequency temporarily (for example to listen to VOLMET), and as a result will be unable to maintain two-way communication, must inform the controlling unit (ordinarily Swanwick(Mil)) of their intentions to leave the frequency and also of their return to it.
4.3.3.2 The Initial Contact Frequency for Swanwick(Mil) is 135.075 MHz.
4.3.3.3 If radio communication is lost, attempts should be made to establish contact with either Newcastle, Teesside International, London or Scottish Control as appropriate to the planned route.
4.3.3.4 If complete radio failure occurs, pilots should follow the standard radio failure procedure detailed at ENR 1.1, paragraph 3.4.
4.4  Western Radar Area of Operation
4.4.1  Area of Operation
4.4.1.1 Provision of ATS outside of controlled airspace within the area defined below is a NATS licensed task provided on a full-time basis by Swanwick(Mil) and by Western Radar depending on the time of day and the flight profile.
  1. 492840N 0045516W - 493146N 0060840W - 510000N 0080000W - 522000N 0053000W - 524406N 0053000W - 525704N 0053000W - 524318N 0050508W - 525038N 0045358W - 531042N 0053000W - 531500N 0053000W - 532315N 0051017W - 532019N 0033502W - 531855N 0031650W - 530313N 0024434W - 521902N 0014707W - 513536N 0012124W - 511623N 0012049W - 510122N 0012720W - 504944N 0013439W - 495813N 0020959W - 495427N 0023012W - 492840N 0045516W.

  2. But excluding:

    1. Danger Areas*;

    2. North Wales MTA.

      Note: * Western Radar may be able to obtain crossing clearance from the appropriate agency.

4.4.2 Vertical limits between FL 100 and FL 195 (FL 245 within active TRAs). The service from Western Radar is intended for (although not exclusively restricted to) aircraft wishing to join or leave Controlled Airspace within the Area of Operation.
4.4.3 Western Radar core operating hours are daily 0645-1930 (0545-1830). Swanwick(Mil) will continue to provide an ATS on a full-time basis subject to unit workload.
4.4.4 Other ATSU's providing a radar service, within the Area of Operation, are:
  1. Lower Airspace Radar Service (LARS) areas of Boscombe Down, Bournemouth, Brize Norton, Cardiff, Culdrose, Exeter, Farnborough North/West, Newquay, Plymouth Military, Shawbury, Valley and Yeovilton;

  2. Swanwick(Mil);

  3. Solent Radar.

4.4.5  Flight Plan Requirements
4.4.5.1 Pilots wishing to receive an ATS from Western Radar are to include within their Flight Plan the Western Radar address EGTTZFZC in addition to any other IFPS address requirements. Failure to address Flight Plans to Western Radar may result in the refusal of service.
4.4.6  Radio Communication
4.4.6.1 Pilots receiving a service who wish to leave the frequency temporarily (for instance to listen to VOLMET), and as a result will be unable to maintain two-way communication, must inform the controlling authority of their intentions to leave the frequency and also of their return to it.
4.4.6.2 The primary frequency for Western Radar is 132.300 MHz.
4.4.6.3 If radio communication is lost, attempts should be made to establish contact with either Swanwick(Mil), Newquay, Exeter, Bournemouth, Brize Norton, London Control or Scottish Control as appropriate to the planned route.
4.4.6.4 If complete radio failure occurs, pilots should follow the standard radio failure procedure detailed at ENR 1.1, paragraph 3.4.
4.5  Off-Shore Operations
4.5.1  Southern North Sea Low Level Air Traffic Services and Helicopter Operating Procedures
4.5.1.1  Introduction
4.5.1.1.1 To enhance flight safety and expedite Search and Rescue in the Southern North Sea Airspace, a Deconfliction Service, Traffic Service, Basic Service and Alerting Service is available from the Air Traffic Service Unit (ATSU) at Aberdeen Airport (Anglia Radar). These services are available to helicopters operating in support to the off-shore oil, gas and renewable industries and to civil and military aircraft transiting the area at and below FL 65.
4.5.1.2  Description

Lateral Limits

Vertical Limits

Controlling Authority Callsign and frequencies Hours

Anglia Radar Area of Responsibility
550000N 0010000W - 550000N 0030301E - 543715N 0025349E - 542245N 0024543E - 535745N 0025155E - 534003N 0025719E - 533503N 0025913E - 532809N 0030055E - 531803N 0030319E - 525551N 0030936E - 523606N 0025307E - 523612N 0014423E then following the coastline to 525655N 0010856E to Strubby (531836N 0001034E) to Easington (533919N 0000706E) - 550000N 0010000W.

FL 65
______

SFC

Anglia Radar (Aberdeen ATSU).

‘Anglia Radar’
Primary: 125.275 MHz
Secondary: 128.925 MHz

Hours: 0630-2200 daily Winter (Summer 1hr earlier).

4.5.1.3 The ATSU will provide, within its specified area of responsibility, Deconfliction Service or Traffic Service within the limits of surveillance cover. Outside surveillance cover or in the event of surveillance failure, a Basic Service and Alerting Service will be provided within the limits of VHF cover. These services will be provided to helicopter pilots routing:
  1. To off-shore installations, until the time that the pilot is in contact with the destination rig/platform;

  2. from off-shore installations, from the time two-way communications is established with the ATSU, until the time that the pilot is in contact with the destination landing pad or other agency.

Note: Under the terms of a Memorandum of Understanding between NATS Limited and the off-shore helicopter companies, aircraft operated by these companies will be provided with modified Flight Information Services, which are prefixed by the term ‘Off-shore’, eg ‘Off-shore Deconfliction Service’.

4.5.1.4  Airspace Structure
4.5.1.4.1  Helicopter Main Routing Indicators (HMRI)
4.5.1.4.1.1 Helicopter Main Routing Indicators are indicators of routes typically and routinely flown by helicopters operating to and from off-shore destinations and are promulgated for the purpose of signposting concentrations of helicopter traffic to other airspace users. HMRI promulgation does not predicate the flow of helicopter traffic. Whilst HMRIs have no airspace status and assume the background airspace classification within which they lie (in the case of the Southern North Sea, Class G), they are used by the air navigation service provider (NATS Ltd/Anglia Radar) and helicopter operators for flight planning and management purposes.
4.5.1.4.1.2 HMRIs have no lateral dimensions. Vertically the HMRIs over the Southern North Sea extend from 1500 FT AMSL to FL 60 (inclusive) except that:
  1. Anglia Radar will not normally allocate cruising levels above FL 40 in the Southern North Sea beneath EGD323D, EGD323E and EGD323K. Where helicopter icing conditions or other flight safety considerations dictate, helicopters may be forced to operate below 1500 FT AMSL.

4.5.1.4.1.3 Compliance with the HMRI structure is not compulsory. In the general interests of flight safety, however, civil helicopter pilots are strongly encouraged to plan their flights using HMRIs wherever possible.
4.5.1.4.1.4 Other traffic operating in proximity of these routes are advised to maintain an alert look out, especially in the Off-shore Safety Area.
4.5.1.4.2 The Southern North Sea HMRI Structure is as follows:

HMRI 1

SORER (524815N 0013445E) to Indefatigable '23A' (*531924N 0023428E);

HMRI 2

SORER (524815N 0013445E) to Windermere (*534954N 0024617E) (Note 1);

HMRI 3

BAGPA (525338N 0012421E) to Munro (*542602N 0021755E) (Note 1);

HMRI 4

BAGPA (525338N 0012421E) to Trent (*541755N 0013930E) (Note 1);

HMRI 5

Waveney (*532109N 0011811E) to Leman '27A' (*530313N 0021358E);

HMRI 6

LAGER (533640N 0000849W) to Viking 'B' (*532648N 0021954E);

HMRI 7

LAGER (533640N 0000849W) to Hyde (*534828N 0010144E) (Note 1);

HMRI 8

LAGER (533640N 0000849W) to Rough 'A' (*534928N 0002811E) to Ravenspurn North (*540150N 0010603E) to Munro (*542602N 0021755E) (Note 1);

HMRI 9

Rough 'A' (*534928N 0002811E) to Cleeton 'PQ' (*540159N 0004336E) (Note 1);

HMRI 10

Cleeton 'PQ' (*540159N 0004336E) to Hyde (*534828N 0010144E) (Note 1);

HMRI 20

Lowestoft (522824N 0014519E) to Inner Gabbard (515450N 0015636E) to Galloper (514710N 0015729E) (Note 2);

HMRI 435

IRDUK (533327N 0025937E) to Carrack (*533444N 0024727E);

HMRI 440

INDEV (531720N 0030331E) to Indefatigable '49/24N' (*531717N 0024316E);

HMRI 445

KUSON (531141N 0030508E) to Indefatigable '49/24N' (*531717N 0024316E);

HMRI 446

KOPAD (530746N 0030615E) to Hewitt '52/5A' (*525956N 0015045E);

HMRI 447

LUVOR (524823N 0030321E) to Hewitt '52/5A' (*525956N 0015045E);

HMRI 450

LUVOR (524823N 0030321E) to RIKPU (524235N 0014227E).

Note 1: The maximum cruising level beneath EGD323D, EGD323E and EGD323K is restricted to FL 40 unless cleared by Anglia Radar.

Note 2: HMRI 20 lies outside the Anglia Area of Responsibility and extends vertically from 500 FT AMSL to 2000 FT AMSL inclusive. There are no ATS service provision arrangements to support operations on this HMRI.

4.5.1.4.3  Off-shore Safety Areas (OSAs). The Anglia OSA consists of the Airspace from surface to 3500 FT ALT within the area bounded by straight lines joining in succession:

533544N 0015732E - 533328N 0021621E - 532200N 0023900E - 531143N 0025505E - 523612N 0014423E then following the coastline to 525242N 0012618E - 532132N 0013545E - 532838N 0014150E - 533544N 0015732E.

4.5.1.4.4  Helicopter Traffic Zones (HTZ). HTZs are established as notification of helicopters engaged in platform approaches, departures and extensive unco-ordinated inter-platform transit flying. Inter-platform flying by civil helicopters within HTZs contained within the OSA will be conducted on the company or field discrete frequency. HTZs consist of the airspace from sea level to 2000 FT ALT contained within tangential lines, not exceeding 5 NM in length, joining the neighbouring circumferences of circles 1.5 NM radius around each individual platform helideck.
4.5.1.4.4.1 The position of individual platforms, together with their maximum height AMSL and helideck height AMSL, within their parent field complex are detailed at paragraph 5.2.
4.5.1.5  Operating Procedures
4.5.1.5.1  General
4.5.1.5.1.1  Helicopter Procedures. Helicopter pilots wishing to use this service must establish two way RTF communication with the ATSU. For flights within the same or adjacent field complex, helicopter pilots should remain on the field frequency. Pilots should advise ATC before changing frequency and/or altitude.
4.5.1.5.1.2  Fixed-Wing Procedures. Pilots of civil and military fixed-wing aircraft intending to fly within the area of responsibility of Anglia Radar are strongly advised to make use of the services provided. Crews of wildlife and aerial survey aircraft should consider utilising notification procedures detailed at ENR 1.1.4 as well as contacting Aberdeen ATSU prior to commencing operations. Whenever possible civil aircraft should be flown above the Transition Altitude at the appropriate level. Pilots are also advised that the helicopters on inter-platform flights in the same field complex normally operate at 500 FT AMSL and frequently carry underslung loads which limit the pilot's ability to take sudden avoiding action.
4.5.1.5.2  Position Reporting; ATC Reports
4.5.1.5.2.1 Position reports on initial contact will include the following information:
  1. Callsign;

  2. Type;

  3. Point of departure;

  4. Point of next landing;

  5. Altitude/requested Altitude;

  6. Total number of people on board.

4.5.1.5.2.2 Subsequent position reports if requested by the ATSU will include the following abbreviated information:
  1. Callsign;

  2. Position;

  3. Altitude.

4.5.1.5.2.3 Helicopter pilots will, prior to leaving a frequency, inform the ATSU of the next off-shore sector to be flown.
4.5.1.5.3  Off-shore Safety Area (OSA)
4.5.1.5.3.1 Pilots of helicopters entering the Anglia OSA should contact Anglia Radar.
4.5.1.5.3.2  Fixed-Wing Procedures. Military and civil pilots of fixed-wing aircraft are recommended to avoid the Anglia OSA, however, if penetration is essential, contact should be made with Anglia Radar no later than 10 NM before entering the area giving their position, altitude, squawk, heading and intentions. When unable to maintain contact with Anglia Radar, and where not previously allocated a squawk by Anglia Radar, pilots should squawk A0007 with ALT (or mode C) selected. Maritime patrol aircraft (MPA) and fisheries protection aircraft should squawk A7300 with ALT (or mode C) selected.
4.5.1.5.4  Cruising Altitudes
4.5.1.5.4.1 Helicopters will normally plan to fly at the following en-route altitudes:
  1. Outbound (land to sea) 2000 FT and 3000 FT AMSL;

  2. Inbound (sea to land) 1500 FT and 2500 FT AMSL;

  3. Inter-field:

    1. Northbound (270° to 089° MAG track) 1000 FT, 2000 FT and 3000 FT AMSL;

    2. Southbound (090° to 269° MAG track) 500 FT, 1500 FT and 2500 FT AMSL.

    Above the Transition Altitude (3000 FT AMSL) all aircraft should conform to the Semicircular Rule.

4.5.1.5.5  Altimeter Setting Procedures
4.5.1.5.5.1 En-route altitudes of 3000 FT AMSL and below will be flown with reference to the appropriate Regional Pressure Setting (RPS). Anglia Radar will give the appropriate pressure setting on first contact. Helicopters operating in this area crossing from one Altimeter Setting Region (ASR) to another, and when in contact with Anglia Radar will not change the RPS datum until instructed to do so. This procedure is to enable the Controller to plan and control vertical separation in the vicinity of an ASR boundary and beneath EGD323D, EGD323E, EGD323K and the Lakenheath ATA North.

Note: When instructed by Anglia Radar to squawk the allocated code, helicopter pilots are requested to state their level to the nearest hundred feet in order that the Mode C transponder information can be verified.

4.5.1.5.6  Use of GPS for North Sea Operations
4.5.1.5.6.1 UK AOC Holders intending to use GPS for en-route navigation for North Sea flight operations are to use GPS equipment that meets or exceeds CAA Specification 22. AOC holders requiring further information should contact their assigned flight operations Inspector. Non UK AOC holders are recommended to operate to at least the Specification 22 standard.
4.5.1.6  Out of Hours Helicopter Operations
4.5.1.6.1 Helicopter off-shore support activity is not confined to published ATS hours and helicopters may be operating in VMC or IMC at all levels and times.
4.5.2  Northern North Sea and Atlantic Rim Low Level Air Traffic Services and Helicopter Operating Procedures
4.5.2.1 To enhance flight safety and expedite Search and Rescue in the Northern North Sea Airspace, including Atlantic Rim Airspace and the East Shetland Basin, a Deconfliction Service, Traffic Service, Basic Service and Alerting Service is available from the Air Traffic Service Unit (ATSU) at Aberdeen Airport. These services are available to helicopters operating in support to the off-shore oil, gas and renewable industries and to civil and military aircraft transiting the area at and below FL 100.
4.5.2.2  Description. Within the areas of responsibility specified below, a Deconfliction Service or Traffic Service within the limits of surveillance cover and, outside surveillance cover or in the event of surveillance failure, a Basic Service and Alerting Service within the limits of VHF cover will be provided. Outside the hours of service notified above, a Basic Service and Alerting Service is available within the limits of VHF RTF cover from the FIR Sector at Scottish ACC, callsign 'Scottish Information' on 129.225 MHz. The above services will be provided to helicopter pilots routing:
  1. To off-shore installations until two-way communication is established with their destination; and

  2. from off-shore installations from the time two-way communication is established with the appropriate Sector.

Lateral Limits (A chart depicting the sectors is at ENR 6-23)

Vertical Limits

Controlling Authorities Callsign and frequencies Hours

Sumburgh Radar Sector — Cormorant QNH Area
This area of responsibility is enclosed by straight lines joining in succession the following points:
602856N 0004429W - 610000N 0002000W - 610000N 0000000E - 605109N 0000000E thence clockwise by the arc of a circle radius 70 NM centred on 595243N 0011712W (SUM VOR) to 600453N 0010000E – 600000N 0010000E - 600000N 0000059E thence anti-clockwise by the arc of a circle radius 40 NM centred on 595243N 0011712W (SUM VOR) to 602856N 0004429W.

FL 85
______

SL

Sumburgh Radar (Aberdeen ATSU)
‘Sumburgh Radar’ – 131.300 MHz and 124.900 MHz (west of meridian 3 degrees West)

Hours:
(all Sumburgh Areas) 0630-2200

(0530-2100)

Sumburgh Radar Sector — Shetland QNH Area
This area of responsibility is enclosed by straight lines joining in succession the following points:
602856N 0004429W thence anti-clockwise by the arc of a circle radius 40 NM centred on 595243N 0011712W (SUM VOR) to 593000N 0022203W - 593000N 0050000W - 610000N 0050000W - 610000N 0002000W - 602856N 0004429W.

FL 85
______

SL

Sumburgh Radar Sector—Sumburgh QNH Area
This area of responsibility, excluding the portion of the MORAY CTA contained within the area, is enclosed by straight lines joining in succession the following points:
600000N 0000059E thence anti-clockwise by the arc of a circle radius 40 NM centred on 595243N 0011712W (SUM VOR) to 593000N 0022203W - 590000N 0021602W – 590000N 0000319W - 594421N 0010000E – 600000N 0010000E - 600000N 0000059E.

FL 85
______

SL

Sumburgh Radar Sector—Aberdeen QNH Area
This area of responsibility, excluding the portion of the MORAY CTA contained within the area, is enclosed by straight lines joining in succession the following points:
590000N 0021602W - 590000N 0000319W – 583242N 0004037W – thence anti-clockwise by the arc of a circle radius 90 NM centred on 571838N 0021602W (ADN VOR) to 584825N 0021817W - 590000N 0021602W.

FL 85
______

SL

Sumburgh Radar Sector — North Sea Area IV
(Delegated ATS, see ENR 2-2-1-1)

This area of responsibility is enclosed by straight lines joining in succession the following points:
610000N 0000000E - 610000N 0040000W - 630000N 0012637W - 630000N 0000000E - 610000N 0000000E.

FL 85
______

SL

Aberdeen Sectors
The area of responsibility, excluding the portion of the MORAY CTA and the Aberdeen CTR/CTA contained within the area, is enclosed by straight lines joining in succession the following points:
584825N 0021817W - 582000N 0024600W - 580946N 0031432W thence anti-clockwise by the arc of a circle radius 5 NM centred on 580539N 0030912W (Beatrice C) to 580313N 0031725W - 572100N 0023356W - 571838N 0021602W (ADN VOR) - 560000N 0013000W - 560000N 0000000E - 560510N 0031455E - 563540N 0023642E - 573628N 0020654E - 575416N 0015748E - 582546N 0012854E - 591722N 0014236E - 595346N 0020430E - 600000N 0020320E - 600000N 0010000E - 594421N 0010000E - 583242N 0004037W - thence anti- clockwise by the arc of a circle radius 90 NM centred on 571838N 0021602W (ADN VOR) to 584825N 0021817W.

FL 85
______

SL

Aberdeen ATSU.
'Aberdeen Radar' 134.100 MHz – within the defined sector, out to ADN 90 DME from the northwestern boundary to the 038 HMRI, and then out to ADN 80 DME clockwise from the 038 HMRI.
135.175 MHz - on and north of 065 HMRI 132.550 MHz - south of 065 HMRI within the Aberdeen sector outwith the areas described above.

Hours:
0630-2200 (0530-2100).

Brent Radar Sector
Area enclosed by straight lines joining in succession the following points:
605109N 0000000E - 620000N 0000000E - 620000N 0012222E - 612122N 0014718E (ALLOY) - 600000N 0020320E - 600000N 0010000E - 600453N 0010000E - thence anti-clockwise by the arc of a circle radius 70 NM centred on 595243N 0011712W (SUM VOR) to 605109N 0000000E.

FL 85
______

SL

Aberdeen ATSU.
‘Brent Radar' - 122.250 MHz is the primary ATC frequency.

Hours:
Mon-Fri 0630-2200 (0530-2100), Sat & Sun 0700-2100 (0600-2000).

East Shetland Basin (ESB)
To co-ordinate the inter-platform and transit helicopter traffic within the ESB, an ATS is established in the area which will provide Flight Information Services. Pilots intending to overfly the ESB below FL 85 are strongly recommended to contact Brent Radar before penetrating the Airspace.

Area enclosed by arcs of circles joining in succession the following points:
614410N 0003900E - 612412N 0003900E (Gate Golf) - 610807N 0004319E (Gate Hotel) - 605828N 0004555E (Gate Juliet) - 604846N 0010430E (Gate Lima) - 604116N 0011454E (Gate Mike) - 603808N 0012042E (Gate November) - 603300N 0014257E (Gate Oscar) - 603300N 0015659E - 612122N 0014718E (ALLOY) - 614410N 0013329E - 614410N 0003900E.

FL 85
______

SL

Aberdeen ATSU.
‘Brent Radar' - 122.250 MHz is the primary ATC frequency.

Hours:
0630-2200 Mon-Fri, 0700-2100 Sat & Sun, Winter (Summer 1hr earlier).

4.5.2.3  Helicopter Main Routing Indicators (HMRI) - En-Route Structure
4.5.2.3.1 Helicopter Main Routing Indicators are indicators of routes typically and routinely flown by helicopters operating to and from off-shore destinations and are promulgated for the purpose of signposting concentrations of helicopter traffic to other airspace users. HMRI promulgation does not predicate the flow of helicopter traffic. Whilst HMRIs have no airspace status and assume the background airspace classification within which they lie (in the case of the Northern North Sea, Class G), they are used by the air navigation service provider (NATS Ltd/ Aberdeen) and helicopter operators for flight planning and management purposes.
4.5.2.3.2 HMRIs have no lateral dimensions. Vertically the HMRIs over the Northern North Sea (55°N to 62°N) extend from 1500 FT AMSL to FL 85 (inclusive), except that:

Where helicopter icing conditions or other flight safety considerations dictate, helicopters may be forced to operate below 1500 FT AMSL.

4.5.2.3.3 Compliance with the HMRI structure is not compulsory. In the general interests of flight safety, however, civil helicopter pilots are strongly encouraged to plan their flights using HMRIs wherever possible.
4.5.2.3.4 Other traffic operating in proximity of these routes are advised to maintain an alert look out, especially in the Off-shore Safety Area (OSA).
4.5.2.3.5  Off-shore Safety Areas (OSAs). The Aberdeen OSA consists of the Airspace from surface to FL 100 within the area bounded by straight lines joining in succession:

590000N 0013755E following the North Sea Median Line (eastern limit of published Aberdeen Sector) to 560510N 0031455E ­ 560441N 0024328E - 571227N 0015238W then anti-clockwise around eastern boundary of the Aberdeen CTR/CTZ to HACKLEY HD (571948N 0015717W) then following the coastline anti-clockwise to 574044N 0015652W - 590000N 0013930W - 590000N 0013755E.

4.5.2.3.6 The HMRI track structure between Sumburgh and the East Shetland Basin is as follows:
  1. HMRI 'Golf' (eastbound) - from 40 DME SUM on HMRI 'Hotel' direct to Gate 'Golf';

  2. HMRI 'Hotel' (eastbound) - from Gate 'Hotel' parallel to HMRI 'Juliet' to 40 DME SUM thence to Sumburgh VOR;

  3. HMRI 'Juliet' (westbound) - from Gate 'Juliet' direct track to Sumburgh VOR;

  4. HMRI 'Lima' (eastbound) - from Sumburgh VOR direct to Gate 'Lima';

  5. HMRI 'Mike' (westbound) - from Gate 'Mike' parallel to HMRI 'Lima' to 40 DME SUM thence to Sumburgh VOR.

4.5.2.3.7  Aberdeen based pilots use HMRIs, a track system centred on 571838N 0021602W (ADN VOR). The system is keyed to the outbound master HMRI 029 commencing at 575506N 0014423W and terminating at Gate 'Lima' (604846N 0010430E) on the ESB boundary. The other HMRIs, spaced at 3 degree intervals, are designated alternately 'inbound' or 'outbound' and are identified by three figures. They terminate at either the appropriate Gate on the ESB boundary or the Median Line. The table below shows co-ordinates for the Gates and the points at which the HMRIs intercept the Median Line. When operating to or from permanent off-shore installations or mobile vessels, pilots normally plan along the nearest HMRI. In the Aberdeen area, HMRIs 023 to 086 (inclusive) are joined to two parallel bi-directional ‘feeder/funnel’ HMRIs, HMRIs Whiskey and Echo. The direction of use of HMRIs Whiskey and Echo is dependent upon the runway in use at Aberdeen. VANOR (571408N 0020304W) and NOBAL (571518N 0020336W) are used as reporting points within the Aberdeen CTR.

HMRI 023

612412N 0003900E (G Gate)

HMRI 074

580248N 0015004E

HMRI 026

605828N 0004555E (J Gate)

HMRI 077

575606N 0015608E

HMRI 029

604846N 0010430E (L Gate)

HMRI 080

574904N 0020028E

HMRI 032

603808N 0012042E (N Gate)

HMRI 083

574153N 0020408E

HMRI 035

603300N 0014257E (O Gate)

HMRI 086

573435N 0020749E

HMRI 038

602326N 0015851E

HMRI 089

572709N 0021133E

HMRI 041

600658N 0020200E

HMRI 092

571931N 0021521E

HMRI 044

595102N 0020249E

HMRI 095

571139N 0021915E

HMRI 047

593014N 0015015E

HMRI 098

570328N 0022316E

HMRI 050

591341N 0014136E

HMRI 101

565455N 0022726E

HMRI 053

590103N 0013811E

HMRI 104

564556N 0023147E

HMRI 056

584942N 0013510E

HMRI 107

563633N 0023535E

HMRI 059

583924N 0013227E

HMRI 110

562416N 0025108E

HMRI 062

582958N 0012959E

HMRI 113

560957N 0030900E

HMRI 065

582221N 0013204E

HMRI 116

555535N 0032034E

HMRI 068

581553N 0013804E

HMRI 071

580923N 0014403E

4.5.2.3.7.1 HMRI Whiskey is aligned along the axis MOCHA (593256N 0012159W) to PETOX (573333N 0014902W) thence to Hackley Head (571949N 0015717W). When Runway 16 is in use at Aberdeen, HMRI Whiskey is the designated inbound track and when Runway 34 is in use HMRI Whiskey is the designated outbound track for traffic planning to operate at 2000 FT and above.
4.5.2.3.7.2 HMRI Echo is aligned along the axis GORSE (571037N 0015351W) to SPIKE (573226N 0013953W) to TYSTI (592224N 0011440W) to TIRIK (593219N 0011214W). When Runway 34 is in use at Aberdeen, HMRI Echo is the designated inbound track but will also be used by outbound traffic planning to operate below 2000 FT. When Runway 16 is in use at Aberdeen, HMRI Echo is the designated outbound track for traffic at all levels.
4.5.2.3.7.3 Helicopter traffic inbound to Aberdeen planning along HMRIs 026 to 086 (inclusive) will be required to maintain the inbound HMRI until intercepting either HMRI Whiskey (Runway 16 in use at Aberdeen) or HMRI Echo (Runway 34 in use at Aberdeen) and then follow the designated inbound track as directed by Aberdeen ATC. Inbound HMRIs south of the HMRI 086 terminate at 30 DME ADN, from whence helicopter traffic will be directed by Aberdeen ATC.
4.5.2.3.7.4 Outbound helicopter traffic utilising the HMRIs 023 to 113 (inclusive) will be directed by Aberdeen to join the desired outbound HMRI via either HMRI Whiskey/Echo or as directed to a specific position on the required HMRI, dependent upon the runway in use at Aberdeen. (Outbound HMRIs south of HMRI 086 commence at 40 DME ADN).
4.5.2.3.7.5 Within the Aberdeen sectors, Aberdeen ATC will allocate ALTs or FLs tactically to participating flights.

Pilots on inter-rigging flights should plan to fly at the following ALTs:

  1. Northbound (270˚ to 089˚ MAG track) 1000 FT, 2000 FT and 3000 FT AMSL;

  2. Southbound (090˚ to 269˚ MAG track) 500 FT, 1500 FT and 2500 FT AMSL.

Note: Under certain operating and meteorological conditions civil helicopters may operate below the base of the HMRIs.

4.5.2.3.8  Aberdeen - Atlantic Rim (West of Shetland Operations)
4.5.2.3.8.1 The HMRI tracks between Aberdeen and the Atlantic Rim (as depicted at ENR 6-27) are as follows:
  1. HMRI X-Ray (Outbound) - ADN VOR (571838N 0021602W) to SMOKI (574637N 0023556W) to WIK VOR (582732N 0030601W) to SODKI (584751N 0033753W) to VAMLA (600000N 0040000W);

  2. HMRI Yankee (Inbound) - NESTA (600000N 0041000W) to MADOX (584343N 0034639W) to WIK VOR (582732N 0030601W).

Note: HMRI X-Ray is bi-directional between Aberdeen and Wick.

4.5.2.3.8.2 Altimeter Setting:
  1. Within 30 DME ADN - Aberdeen QNH, or as directed by ATC;

  2. Outside 30 DME ADN - The appropriate Regional Pressure Setting (RPS), or as directed by ATC.

Note: To enable controllers to plan and control vertical separation near the boundaries of Altimeter Setting Regions (ASR), helicopters approaching an ASR boundary, and in radio contact with ATC, are not to change RPS until instructed to do so.

4.5.2.3.8.3 Cruising altitudes:

Within the Aberdeen sectors, Aberdeen ATC will allocate ALTs or FLs tactically to participating flights.

Note: Under certain operating and meteorological conditions civil helicopters may operate below the base of the HMRIs.

4.5.2.3.8.4 Moray Firth TMZ Phase 1 Controlling Authority Lossie Departures (119.575 MHz), active H24, see ENR 2.2 paragraph 4.
4.5.2.3.9 Charts depicting the Aberdeen Area HMRI track structure are at AD 2-EGPD-3-1/2. The chart at ENR 6-26 depicts the en-route HMRI track structure and shows the bi-directional HMRI established between the Ekofisk Hotel platform and platform P37/4, a route normally used by Norwegian helicopters.
4.5.2.4  Operating Procedures
4.5.2.4.1  General
4.5.2.4.1.1  Helicopter Procedures. Helicopter pilots wishing to use the service specified in paragraph 4.5.2.2 must file a flight plan. Pilots who have established two-way communication with the appropriate Sector and subsequently do not receive acknowledgement of a scheduled position report, should make every effort to relay the report via another aircraft or agency. For flights within the same or adjacent field complexes, helicopter pilots should maintain RTF contact on the field, company or Traffic Area frequency. Position reports by civil helicopter pilots operating on HMRIs are to be based on distance from either Aberdeen or Sumburgh VORs, according to the departure or destination aerodrome. Position reports are only required if the flight is not receiving a radar service from the ATSU. In this instance, unless otherwise specified by the ATSU, an initial report is to be made on outbound HMRIs at 40 NM and then at 20 NM intervals, subject to the limitations of VHF cover. For inbound flights subsequent to the initial call, reports are to be made at the same 20 NM intervals according to the destination aerodrome. If the elapsed time between two reporting points exceeds 15 minutes, an additional report is to be made after 15 minutes elapsed time since the last report.

En-route position reports are to include the following information:

  1. Callsign;

  2. Position (HMRI and range);

  3. ALT or FL;

  4. Position of next intended report.

On lifting from an installation or ship off-shore, the initial report is to include:

  1. Callsign;

  2. Actual position and altitude;

  3. Requested HMRI and point of joining;

  4. Requested altitude;

  5. Total persons on board.

4.5.2.4.1.2  Fixed-Wing Procedures. Pilots of civil and military fixed-wing aircraft intending to fly within the areas of responsibility of the above Sectors are strongly advised to make use of the services provided. Crews of wildlife and aerial survey aircraft should consider utilising notification procedures detailed at ENR 1.1.4 as well as contacting Aberdeen ATSU prior to commencing operations. Whenever possible civil aircraft should be flown above the Transition Altitude at the appropriate level. Pilots are advised that helicopters engaged on inter-platform flights within the same field complex normally operate at about 500 FT AMSL and frequently carry underslung loads which limit the pilot's ability to take sudden avoidance action.
4.5.2.4.2  Off-shore Safety Area (OSA)
4.5.2.4.2.1 Pilots of helicopters entering the Aberdeen OSA should follow procedures detailed in paragraph 4.5.2.4.1.1.
4.5.2.4.2.2  Fixed-Wing Procedures . Where penetration of the Aberdeen OSA is essential, contact should be made on the appropriate Aberdeen frequency (paragraph 4.5.2.2) no later than 10 NM before entering the OSA giving their position, altitude, squawk, heading and intentions. Military pilots not previously in contact with the ASACS should call Boulmer ICF (259.225) or the appropriate Aberdeen frequency. Where pilots are unable to maintain contact on the appropriate Aberdeen frequency or the ASACS, and when not previously allocated a squawk, they should squawk A0007 with ALT (or mode C) selected. Maritime patrol aircraft (MPA) and fisheries protection aircraft should squawk A7300 with ALT (or mode C) selected.
4.5.2.4.2.3  General Procedures. Within the Sumburgh Radar and Brent Radar sectors, Aberdeen ATC will allocate ALTs or FLs tactically to participating flights.
4.5.2.4.2.4  Off-shore Operations. Helicopter off-shore support activity is not confined to published ATS hours and helicopters may be operating in VMC or IMC at all levels and times.
4.5.2.4.2.4.1 The positions of individual platforms within their parent field complex are detailed at paragraph 4.5.5.2.
4.5.2.4.2.5 Within the Aberdeen ATSU Areas of Responsibility as described in paragraph 4.5.2.2, during the published hours of operation, the following QNH values will be used:
  1. Brent Radar Sector and northern area of the Sumburgh Radar Sector - Cormorant QNH. If the actual Cormorant QNH data is lost, the Puffin or Marlin will be used as appropriate.

  2. Central and eastern area of the Sumburgh Radar Sector - Sumburgh QNH.

  3. Western area of the Sumburgh Radar Sector - Shetland Regional QNH.

  4. Southern area of the Sumburgh Radar Sector, south of 59N – Aberdeen QNH.

  5. Aberdeen Sector out to ADN DME 90 - Aberdeen QNH.

  6. Aberdeen Sector beyond ADN DME 90 and north of HMRI 086 - Brae QNH. (If Brae QNH data is lost the Weller QNH will be used, this being the lower of the Rattray or Petrel RPS.)

  7. Aberdeen Sector beyond ADN DME 90 and south of HMRI 086 - Fulmar QNH. (If Fulmar QNH data is lost the McCabe QNH will be used, this being the lower of the Rattray or Skua RPS.)

  8. Aircraft routing on HMRI 086 will be instructed to set the most appropriate QNH for the traffic situation.

    Note: See chart at ENR 6-23 for areas.

4.5.2.4.2.5.1 Transition level within the above areas will be determined with reference to the above pressure settings.
4.5.2.4.2.6  Use of GPS for North Sea Operations
4.5.2.4.2.6.1 UK AOC Holders intending to use GPS for en-route navigation for North Sea flight operations are to use GPS equipment that meets or exceeds CAA Specification 22. AOC holders requiring further information should contact their assigned flight operations Inspector. Non UK AOC holders are recommended to operate to at least the Specification 22 standard.
4.5.2.5  Sumburgh CTR Helicopter Procedures
4.5.2.5.1  Standard Arrival and Departure Routes
4.5.2.5.1.1 The Standard Arrival and Departure Routes are established for use in conjunction with the HMRIs and are shown at AD 2-EGPB-3-1/2. The route orientation is dependant on the runway-in-use as follows:
  1. Westerly Operation (Runways 27 and 33 in use):

    Departures for the East Shetland Basin are to route via BODAM (595506N 0011606W) and those for HMRIs Whiskey/Echo are to route via SILOK (594612N 0012900W);

    Arrivals from the East Shetland Basin are to route via IZACK (595327N 0010113W) and those from HMRIs Whiskey/Echo are to route via BENTY (594615N 0010810W).

  2. Easterly Operation (Runways 09 and 15 in use):

    Departures for the East Shetland Basin are to route via IZACK and those for HMRIs Whiskey/Echo are to route via BENTY;

    Arrivals from the East Shetland Basin are to route via BODAM and those from HMRIs Whiskey/Echo are to route via SILOK.

4.5.2.5.1.2 Additionally, to assist in the integration of flights operating under VFR or, at night, in accordance with a Special VFR clearance, VFR/SVFR flights may be instructed to route via Mousa Lighthouse Visual Reference Point. (See AD 2-EGPB­2.22 paragraph 2).
4.5.2.5.2  Helicopter Holding Patterns
4.5.2.5.2.1  IFR Holding Patterns. IFR holding patterns are established at Juliet 20, Mike 20, MOCHA and TIRIK. The holds are 1-minute left-hand patterns aligned on the HMRI inbound track.
4.5.2.5.2.2  Visual Holding Patterns. Visual holding patterns are established at BODAM, Mousa Lighthouse VRP, IZACK, BENTY and SILOK. Holding is to be conducted clear of cloud and in sight of the surface and helicopters will adopt a 2 minute left-hand orbit, except at BENTY which is right-hand. Maximum holding altitude 1000 FT AMSL.
4.5.3  Morecambe Bay and Liverpool Bay Gas Fields - Helicopter Support Flights
4.5.3.1 Permanent platforms positioned on the Morecambe Bay and Liverpool Bay Gas Fields are shown at ENR 6-28.
4.5.3.2  Helicopter Traffic Zone (HTZ)
4.5.3.2.1 A Helicopter Traffic Zone (HTZ), established as notification of helicopters engaged in platform approaches, departures and extensive unco-ordinated inter-platform transit flying, is established around the Morecambe Bay and Liverpool Bay Gas Fields. A HTZ consists of the airspace from sea level to 2000 FT AMSL contained within the tangential lines, not exceeding 5 NM in length, joining the neighbouring circumferences of circles 1.5 NM radius around each individual platform helideck.
4.5.3.3  Airspace Structure - Morecambe Bay
4.5.3.3.1 The helicopter support land base is Blackpool Airport. Low level flights, normal operating height 1000 FT AMSL or above on the Blackpool QNH, operate daily between Blackpool Airport and the helidecks. Under certain operating and meteorological conditions civil helicopters may operate below 1000 FT AMSL on the Blackpool QNH.
4.5.3.3.2 The route structure is:

Blackpool to Point 'N' (534922N 0030858W) to DP4.

Note 1: Point 'N' may be used as a holding point.

Note 2: Route is bi-directional.

4.5.3.3.3 Helicopter traffic information is available from Blackpool Approach during published hours of operation.
4.5.3.3.4 Pilots are warned that gas release and burn-off operations may take place at any time without prior notification from off­shore gas installations.
4.5.3.4  Airspace Structure - Liverpool Bay
4.5.3.4.1 The helicopter support land base is Blackpool Airport. Low level flights, normal operating height 1000 FT AMSL on the Blackpool QNH, operate daily between Blackpool Airport and the helidecks. Transit height to/from the Lennox platform is 500 FT AMSL. Flights between helidecks are normally conducted between 500 FT and 1000 FT.
4.5.3.4.2 The route structure is:
  1. Blackpool to Gate G (534449N 0030441W) to Hamilton (533357N 0032716W);

  2. Blackpool to Gate G to Lennox (533719N 0031037W).

    Note: Routes are bi-directional.

4.5.3.4.3 Helicopter traffic information is available from Warton Approach during the Warton ATC published hours of operation. Outside these hours, information is available from Blackpool Approach.
4.5.3.4.4 Gas release and burn-off operations may take place at any time without prior notification from off-shore gas installations.
4.5.3.4.5 Burbo Bank TMZ Controlling Authority Warton, (APP 129.530 MHz), active Mon-Thu 0730-1900 (0630-1800), Fri 0730-1700 (0630-1600). See ENR 2.2.
4.5.3.4.6 Walney TMZ Controlling Authority Warton, (APP 129.530 MHz), active Mon-Thu 0730-1900 (0630-1800), Fri 0730-1700 (0630-1600). See ENR 2.2.
4.5.3.5  Altimeter Setting
4.5.3.5.1 The Blackpool QNH will be used by helicopter support flights in transit to and from Blackpool Airport, and within the Morecambe Bay and Liverpool Bay Gas Fields.
4.5.4  Flight Plan Procedures for Helicopter Operations over Sea Areas around the United Kingdom
4.5.4.1 Pilots are warned of the need to consider application of the procedures detailed at ENR 1-10-4 paragraph 1.11, when operating under both VFR and IFR in support of off-shore facilities (particularly over the Southern and Northern North Sea, Atlantic Rim and Morecambe and Liverpool Bays). When flying to a location without an ATSU or AFTN link, nomination of a responsible person is vital to guarantee the initiation of alerting action in the event of non-arrival.
4.5.5  RTF and NDB Frequencies Used on Off-shore Installations
4.5.5.1  General
4.5.5.1.1 All Operators wishing to establish an aeronautical radio station within the UK Off-shore Areas under concession are required to obtain regulatory approval from the Civil Aviation Authority prior to operating that radio station.
4.5.5.1.1.1 Application for approval to establish and operate an aeronautical radio station on fixed or mobile installations must be made to Ofcom:
Post:

Spectrum Licensing, PO Box 1285, Warrington, WA1 9GL.

Tel: 020-7981 3131.

Email: spectrum.licensing@ofcom.org.uk

URL: www.ofcom.org.uk/manage-your-licence

This application will then be passed to the Civil Aviation Authority (CAA) for approval. Following the approval process, operators of radio stations should hold the following:

  1. An equipment approval under the Air Navigation Order (ANO), issued by the CAA;

  2. A frequency assignment, issued by the CAA;

  3. An aeronautical radio licence under the Wireless Telegraphy Act 2006 (’the WT Act’), issued by Ofcom.

Applicants should note that coordination with other European states may be necessary before a frequency assignment can be made; applications for approval should be made as early as possible and can be made up to six months before operationally required.

4.5.5.1.2 Frequencies listed for fixed installations and the frequency plan for mobile installations in UK Areas Under Concession.
  1. Information on frequencies in use by the off-shore helicopter community can be obtained from the Helideck Certification Agency at http://www.helidecks.org/index.php/helideck-certificates;

  2. Mobiles must operate in accordance with the frequency plan shown in paragraph 4.5.5.3;

  3. Aeronautical RTF operations for all installations north of 56°N and east of 5°W and within the UK Off-shore Areas Under Concession, with the exception of the East Shetland Basin – that is Off-shore RTF Areas A to I (Note 1) – have each been provided with two RTF frequencies, one for Traffic (Note 2) RTF calls and the other for Logistics (Note 3) RTF calls, as listed in paragraph 4.5.5.3.1. No suffix will be added to the Civil Aviation Authority approved callsign when traffic information is to be passed by the operator of the aeronautical radio station. When logistics information is to be passed the suffix ‘LOG’ shall be added to the approved callsign.

Simultaneous operation of the traffic and the LOG frequencies may be required, installations are therefore required to carry radio facilities to support this.

Note 1: Operators wishing to operate installations in Area X on the RTF frequency allocations chart should contact the Authority at least 90 days before operation is required in order to obtain a temporary RTF frequency assignment.

Note 2: The Traffic frequency is to be used for giving information on aircraft positions, obtaining deck clearance, and for lifting calls.

Note 3: The logistics (LOG) frequency should be used for all other calls permitted within the terms of an OPC service such as, departure messages, in-field routings, payload information, and ordering fuel and refreshments.

RTF Operation - Areas A to P: RTF frequency assignments for off-shore installations may only be used for communication between installations and aircraft that are both within the same off-shore RTF frequency assignment area. The Traffic frequencies may be used for communication with aircraft that are below 2000 FT and the LOG frequencies may be used for communication with aircraft that are below 7000 FT

Published Air Traffic Service procedures should be followed where available. A listening watch should be maintained with the Air Traffic Service Unit (ATSU) where possible. Prior to leaving the ATSU’s operating area, pilots should advise the ATSU of the aircraft’s movement intentions. Where maintaining a listening watch with the ATSU is not possible and at all times when the aircraft is below 1500 FT a listening watch on the RTF Area Traffic Frequency shall be maintained.

Outbound - To the off-shore installation: Pilots who are in communication with the ATSU should, once established in the descent and still above 1500 FT, establish contact with their destination on the Area Traffic Frequency, and hand over the flight watch. They should then advise the ATSU on passing 1500 FT. Landing clearances should be obtained from the HLO who will be operating on the Traffic frequency.

Inbound - From the off-shore installation: Lifting calls should be made on the Traffic frequency. Once airborne establish communication with the appropriate ATSU whilst below 1000 FT or as soon practical. Published Air Traffic Service procedures should be followed where available.

The appropriate LOG frequency should be used as required to exchange information with the destination. When operating below 1500 FT or outside the ATSU’s area of operation pilots should retune the ATSU radio to the LOG frequency for passing Logistics information. When not being used for LOG messages the radio should be retuned to monitor the appropriate ATSU’s frequency.

4.5.5.1.3 Offshore installation’s VHF RTF facilities and aeronautical Non Directional Beacons operate by arrangement only; the unserviceability of these facilities will NOT be promulgated by NOTAM.
4.5.5.1.4  NDBs on both fixed and mobile installations generally operate on shared frequencies. NDBs that share frequencies should only be switched on if requested by the helicopter pilot and then only after the frequency has been monitored by the pilot and found to be vacant immediately prior to switching on. The pilot should advise the NDB operators as soon as they no longer require the use of the NDB. When no longer required the NDB should be switched off. Additionally, in order to assist helicopters transiting fields a small number of NDBs on fixed installations have been assigned frequencies that enable them to operate as close to H24 as practical. Pilots may find these NDBs already on and that they remain on after they have advised the installation that they no longer require their use.
4.5.5.1.5 Flight Information Services are provided by NATS Limited from Aberdeen in the Aberdeen ATSU Off-shore Areas of Responsibility (ENR 6-23 and 6-25).
4.5.5.2  RTF and NDB Frequencies/Channels for Fixed Installations
4.5.5.2.1 Data on RTF and NDB frequencies/channels in use by the off-shore helicopter community can be obtained from the Helideck Certification Agency at http://www.helidecks.org/index.php/helideck-certificates.
4.5.5.3  RTF and NDB Frequencies/Channels used on Off-shore Installations in the UK Areas under Concession
4.5.5.3.1 RTF Frequencies/Channels for Off-shore Installations.

Area

Boundaries

VHF RTF Channel

Traffic

LOG

A

583736N 0050000W - 602049N 0050000W - 602106N 0045640W - 602405N 0044416W - 604743N 0041832W - 605149N 0041400W - 605459N 0041030W - 610245N 0040352W - 610427N 0040226W - 610739N 0035937W - 612137N 0034754W - 614500N 0031304W - 614500N 0003400W - 595244N 0011712W - 574200N 0014713W - 574200N 0035805W thence along the UK East Coast to 583736N 0050000W.

122.805

129.130

B

574200N 0014713W - 595244N 0011712W - 614500N 0003400W - 614410N 0003900E ­ 612412N 0003900E - 610807N 0004319E - 605828N 0004555E - 604846N 0010430E ­ 604116N 0011454E - 603808N 0012042E - 603300N 0014257E - 603300N 0015659E ­ 602324N 0015851E - 574200N 0014648W - 574200N 0014713W.

122.805

129.130

C

602324N 0015851E - 595346N 0020430E - 591722N 0014236E - 591340N 0014136E ­ 584026N 0002838E thence anti-clockwise by the arc of a circle radius 120 NM centred on 571838N 0021602W (ADN VOR) to 585707N 0000719W - 602324N 0015851E.

122.180

125.405

D

591340N 0014136E - 582546N 0012854E - 582430N 0013034E - 581627N 0010020E thence anti-clockwise by the arc of a circle radius 120 NM centred on 571838N 0021602W (ADN VOR) to 584026N 0002838E - 591340N 0014136E.

123.655

129.130

E

585707N 0000719W thence clockwise by the arc of a circle radius 120 NM centred on 571838N 0021602W (ADN VOR) - 581627N 0010020E - 573123N 0013500W ­ 574200N 0013500W - 574200N 0014648W - 585707N 0000719W.

123.005

128.405

F

582430N 0013034E - 580500N 0014803E - 572707N 0013500W - 573123N 0013500W ­ 582430N 0013034E.

123.555

126.405

G

580500N 0014803E - 575416N 0015748E - 573927N 0020521E - 572231N 0013500W - 572707N 0013500W - 580500N 0014803E.

122.005

126.355

H

573927N 0020521E - 564859N 0023018E - 571506N 0013500W - 572231N 0013500W - 573927N 0020521E.

122.330

129.705 (Shell 130.880)

I

564859N 0023018E - 563540N 0023642E - 560510N 0031455E - 560000N 0031758E - 560000N 0013500W - 571506N 0013500W - 564859N 0023018E.

122.780

126.805 (Shell 130.880)

J

560000N 0031758E - 555004N 0032355E - 543715N 0025349E - 542245N 0024543E ­ 525851N 0005830E thence along the UK East Coast - 560000N 0023000W ­ 560000N 0031758E.

122.230

122.230

K

542245N 0024543E - 535745N 0025155E - 534003N 0025719E - 533503N 0025913E ­ 532809N 0030055E - 531803N 0030319E - 525551N 0030936E - 520000N 0022345E ­ 520000N 0012528E thence along the UK East Coast - 525851N 0005830E ­ 542245N 0024543E.

130.280

130.280

 

In some circumstances the following may apply:

  
 

(a)

The Leman/Sean Indefatigable Fields use

123.630

123.630

 

(b)

The Esmond/Forbes/Gordon Fields use

122.330

122.330

 

(c)

The Rough/West Sole Fields and Villages use

129.880

129.880

 

(d)

The Viking Field use

118.655

118.655

 

(e)

The Viking/Ann Field use

123.580

123.580

 

(f)

The Hewett/Arpet Fields use

122.880

122.880

 

(g)

The Thames Field use

123.230

123.230

 

(h)

The Ravenspurn Field use

123.030

123.030

 

(i)

The Cleeton/West Sole Fields and Villages use

130.730

130.730

L

550000N 0051004W thence along the UK West Coast - 530000N 0042542W ­ 530000N 0051200W - 540000N 0051200W - 540000N 0060608W thence along the Northern Ireland East Coast - 550000N 0055911W - 550000N 0051004W.

122.380

122.380

  

In some circumstances the following may apply:
Liverpool Bay Fields use

129.780

129.780

M

595000N 0050000W - 583736N 0050000W - 583100N 0061538W thence along the UK West Coast to 580000N 0070542W - 580000N 0100000W - 595952N 0100000W - 595627N 0090040W - 601845N 0052412W - 602049N 0050000W - 595000N 0050000W.

123.255

123.255

N

580000N 0070542W thence along the UK West Coast - 554000N 0063000W ­ 554000N 0064800W - 555000N 0064800W - 555000N 0070000W - 560000N 0070000W ­ 560000N 0080000W - 561000N 0080000W - 561000N 0084800W - 562000N 0084800W ­ 562000N 0093000W - 562312N 0100000W - 580000N 0100000W - 580000N 0070542W.

130.155

130.155

O

595952N 0100000W - 562312N 0100000W - 570000N 0192700W - 595000N 0142600W ­ 594957N 0131612W - 600902N 0131612W - 600718N 0121737W - 600250N 0111627W ­ 600208N 0105047W - 600057N 0102051W - 595952N 0100000W.

122.230

122.230

P

530000N 0051900W - 530000N 0042542W thence along the UK South Coast to 520000N 0012528E - 520000N 0023831E - 514957N 0023015E - 513647N 0021512E ­ 513328N 0021418E - 513014N 0020718E - 512011N 0020218E - 511935N 0020143E ­ 511424N 0015713E - 510555N 0014326E - 510216N 0013248E - 505657N 0012120E ­ 505344N 0011653E - 504747N 0011523E - 503835N 0010721E - 502319N 0004634E ­ 501938N 0003607E - 501409N 0000209E - 501310N 0001535W - 500726N 0003005W ­ 500824N 0010005W - 500912N 0013005W - 500911N 0020331W - 495747N 0024829W ­ 494627N 0025635W - 493827N 0032105W - 493309N 0033455W - 493239N 0034249W ­ 493205N 0035552W - 492736N 0041759W - 492719N 0042151W - 492310N 0043244W ­ 491424N 0051105W - 491256N 0052045W - 491206N 0054035W - 481257N 0091200W ­ 481000N 0092216W - 481000N 0100000W - 482000N 0100000W - 482000N 0094800W ­ 483000N 0094800W - 483000N 0093600W - 485000N 0093600W - 485000N 0092400W ­ 490000N 0092400W - 490000N 0091700W - 490956N 0091705W - 490956N 0091205W ­ 492000N 0091200W - 492000N 0090300W - 493000N 0090300W - 493000N 0085400W ­ 494000N 0085400W - 494000N 0084500W - 494956N 0084505W - 494956N 0083605W ­ 495956N 0083605W - 495956N 0082405W - 500956N 0082405W - 500956N 0081205W ­ 502000N 0081200W - 502000N 0080000W - 502956N 0080005W - 502956N 0073605W ­ 503956N 0073605W - 503956N 0071205W - 505000N 0071200W - 505000N 0070300W ­ 510000N 0070300W - 510000N 0064800W - 511000N 0064800W - 511000N 0064200W ­ 512000N 0064200W - 512000N 0063300W - 513000N 0063300W - 513000N 0061800W ­ 514000N 0061800W - 514000N 0060600W - 515000N 0060600W - 515000N 0060000W ­ 515400N 0060000W - 515400N 0055700W - 515800N 0055700W - 515800N 0055400W ­ 520000N 0055400W - 520000N 0055000W - 520400N 0055000W - 520400N 0054600W ­ 520800N 0054600W - 520800N 0054200W - 521200N 0054200W - 521200N 0053900W ­ 521600N 0053900W - 521600N 0053500W - 522400N 0053500W - 522400N 0052248W ­ 523200N 0052248W - 523200N 0052800W - 524400N 0052800W - 524400N 0052430W ­ 525200N 0052430W - 525200N 0052230W - 525900N 0052230W - 525900N 0051900W ­ 530000N 0051900W.

122.780

122.780

ESB

614410N 0003900E - 612412N 0003900E (Gate Golf) - 610807N 0004319E (Gate Hotel) - 605828N 0004555E (Gate Juliet) - 604846N 0010430E (Gate Lima) - 604116N 0011454E (Gate Mike) - 603808N 0012042E (Gate November) - 603300N 0014257E (Gate Oscar) - 603300N 0015659E - 612122N 0014718E (ALLOY) - 614410N 0013329E - 614410N 0003900E.

129.405

129.405

4.5.5.3.2 NDB Frequencies for Mobiles

Within the East Shetland Basin (ESB)

614410N 0003900E - 614410N 0013329E - 612122N 0014718E (ALLOY) - 612000N 0014735E - 612000N 0004008E - 612412N 0003900E - 614410N 0003900E.

553.5

20

612000N 0004008E - 612000N 0014735E - 610000N 0015138E - 610000N 0004530E ­ 610807N 0004319E - 612000N 0004008E.

597.5

20

610000N 0004530E - 610000N 0015138E - 603300N 0015659E - 603300N 0014257E ­ 603808N 0012042E - 604116N 0011454E - 604846N 0010430E - 605828N 0004555E ­ 610000N 0004530E.

579.5

20

1

635313N 0002927W - 633809N 0003007W - 633809N 0001106W - 625328N 0003821E - 622219N 0010622E - 614410N 0013329E - 614410N 0003900E - 612412N 0003900E - 610807N 0004319E - 605828N 0004555E - 604846N 0010430E - 604116N 0011454E - 603808N 0012042E - 603300N 0014257E - 603300N 0015659E - 595346N 0020430E - 591722N 0014236E - 590000N 0013755E - 590000N 0050000W - 602049N 0050000W - 602106N 0045640W - 602405N 0044416W - 604743N 0041832W - 605149N 0041400W - 605459N 0041030W - 610245N 0040352W - 610427N 0040226W - 610739N 0035937W - 612137N 0034754W - 615207N 0031144W - 615914N 0030320W - 634039N 0004744W - 635313N 0002927W.

588.5

20

2

590000N 0002400E - 570000N 0002400E - 570000N 0021012W thence along the UK East Coast to 583736N 0050000W - 590000N 0050000W - 590000N 0002400E.

597.5

20

590000N 0002400E - 590000N 0013755E - 582546N 0012854E - 575416N 0015748E ­ 570000N 0022458E - 570000N 0002400E - 590000N 0002400E.

553.5

20

570000N 0022458E - 563540N 0023642E - 560510N 0031455E - 560000N 0031758E ­ 560000N 0023000W thence along the East Coast of Scotland to 570000N 0021012W ­ 570000N 0022458E.

897.0

20

4A

560000N 0031758E - 555004N 0032355E - 543715N 0025349E - 542245N 0024543E ­ 525851N 0005830E thence along the UK East Coast to 560000N 0023000W ­ 560000N 0031758E.

949.0 (†)

20

4B

542245N 0024543E - 535745N 0025155E - 534003N 0025719E - 533503N 0025913E ­ 532809N 0030055E - 531803N 0030319E - 525551N 0030936E - 520000N 0022345E ­ 520000N 0012528E thence along the UK East Coast to 525851N 0005830E ­ 542245N 0024543E.

579.5 (‡) 897.0 (‡)

20

5

550000N 0051004W thence along the UK West Coast - 530000N 0042542W ­ 530000N 0051200W - 540000N 0051200W - 540000N 0060608W thence along the N Ireland East Coast to 550000N 0055911W - 550000N 0051004W.

597.5

20

6

595000N 0050000W - 583736N 0050000W - 583100N 0061538W thence along the UK West Coast to 580000N 0070542W - 580000N 0100000W - 595952N 0100000W - 595627N 0090040W - 601845N 0052412W - 602049N 0050000W - 595000N 0050000W.

579.5

20

7

580000N 0070542W thence along the UK West Coast to 554000N 0063000W ­ 554000N 0064800W - 555000N 0064800W - 55000N 0070000W - 560000N 0070000W ­ 560000N 0080000W - 561000N 0080000W - 561000N 0084800W - 562000N 0084800W ­ 562000N 0093000W - 562312N 0100000W - 580000N 0100000W - 580000N 0070542W.

553.5

20

 

(†) Area 4a NDB/VHF pairing — 949.0 kHz/122.225 MHz.

(‡) Area 4b NDB/VHF pairing — 579.5 kHz/130.275 MHz or 897.0 kHz/130.275 MHz.

For Notes See End of Table.

  

8

595952N 0100000W - 562312N 0100000W - 570000N 0192700W - 595000N 0142600W ­ 594957N 0131612W - 600902N 0131612W - 600718N 0121737W - 600250N 0011627W - 600208N 0105047W - 600057N 0102051W - 595952N 0100000W.

897.0

20 min
50 max

9

530000N 0051900W - 530000N 0042542W thence along the UK South Coast to 520000N 0012528W - 520000N 0023831E - 514957N 0023015E - 513647N 0021512E ­ 513328N 0021418E - 513014N 0020718E - 512011N 0020218E - 511935N 0020143E ­ 511424N 0015713E - 510555N 0014326E - 510216N 0013248E - 505657N 0012120E ­ 505344N 0011653E - 504747N 0011523E - 503835N 0010721E - 502319N 0004634E ­ 501938N 0003607E - 501409N 0000209E - 501310N 0001535W - 500726N 0003005W ­ 500824N 0010005W - 500912N 0013005W - 500911N 0020331W - 495747N 0024829W ­ 494627N 0025635W - 493827N 0032105W - 493309N 0033455W - 493239N 0034249W ­ 493205N 0035552W - 492736N 0041759W - 492719N 0042151W - 492310N 0043244W ­ 491424N 0051105W - 491256N 0052045W - 491206N 0054035W - 481257N 0091200W ­ 481000N 0092216W - 481000N 0100000W - 482000N 0100000W - 482000N 0094800W ­ 483000N 0094800W - 483000N 0093600W - 485000N 0093600W - 485000N 0092400W ­ 490000N 0092400W - 490000N 0091700W - 490956N 0091705W - 490956N 0091205W ­ 492000N 0091200W - 492000N 0090300W - 493000N 0090300W - 493000N 0085400W ­ 494000N 0085400W - 494000N 0084500W - 494956N 0084505W - 494956N 0083605W ­ 495956N 0083605W - 495956N 0082405W - 500956N 0082405W - 500956N 0081205W ­ 502000N 0081200W - 502000N 0080000W - 502956N 0080005W - 502956N 0073605W ­ 503956N 0073605W - 503956N 0071205W - 505000N 0071200W - 505000N 0070300W ­ 510000N 0070300W - 510000N 0064800W - 511000N 0064800W - 511000N 0064200W ­ 512000N 0064200W - 512000N 0063300W - 513000N 0063300W - 513000N 0061800W ­ 514000N 0061800W - 514000N 0060600W - 515000N 0060600W - 515000N 0060000W ­ 515400N 0060000W - 515400N 0055700W - 515800N 0055700W - 515800N 0055400W ­ 520000N 0055400W - 520000N 0055000W - 520400N 0055000W - 520400N 0054600W ­ 520800N 0054600W - 520800N 0054200W - 521200N 0054200W - 521200N 0053900W ­ 521600N 0053900W - 521600N 0053500W - 522400N 0053500W - 522400N 0052248W ­ 523200N 0052248W - 523200N 0052800W - 524400N 0052800W - 524400N 0052430W ­ 525200N 0052430W - 525200N 0052230W - 525900N 0052230W - 525900N 0051900W ­ 530000N 0051900W.

435

20

Note 1: Simultaneous operation of NDBs on the same frequency by more than one mobile installation is likely to result in incorrect navigational information being displayed to pilots. For this reason it is essential that NDB operators read and comply with Notes regarding off-shore radio facilities. CAA Doc 446 is available from the department detailed at paragraph 4.5.5.1.1.1.

Note 2: Alternative arrangements may be desirable for flight safety reasons when working adjacent to a permanent installation. These will be agreed by the CAA in consultation with the parties concerned. Where the mobile installation temporarily uses the RTF frequency assigned to the permanent installation, helicopters will not normally use the mobile NDB because of the difficulty in co-ordinating with other users of the same NDB frequency.

Note 3: If NDB operation does become necessary the appropriate NDB frequency shown in the diagram at ENR 6-31 is to be used and the helicopter company involved is requested to co-ordinate use with other mobiles on the appropriate area frequency.